OpenAM Reflected XSS in the OAuth2/OIDC `wap` consent page

CVE Details

• Protection status: Protected by Atomicorp rules · About protection statuses
• CVE: CVE-2026-62280
• Name: OpenAM Reflected XSS in the OAuth2/OIDC wap consent page
• Severity: Medium
• CVSS: 6.1 (v3.1) (Medium)
• CVSS version: 3.1
• CVSS source: GitHub_M CNA
• CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
  • Attack vector: Network
  • Attack complexity: Low
  • Privileges required: None
  • User interaction: Required
  • Scope: Changed
  • Confidentiality impact: Low
  • Integrity impact: Low
  • Availability impact: None
• CWE: CWE-79
• Vendor: OpenIdentityPlatform
• Vulnerable product: OpenAM
• CVE published: 2026-09-15
• CVE last modified: 2026-09-15
• EPSS: 0.0021; 11.5th percentile as of 2026-09-16 (FIRST (opens in a new tab) )
• Latest Update: 2026-09-16
• Selected Rule IDs observed: 333140 , 333141 , 340087 , 340095 , 340099 , 340147 , 340148 , 341099 , 341256 , 341266 , 342259 , 346755 , 350147 , 350148
• Matching rules: 14; rules with blocking actions: 14
• Would-block Rule IDs: 333140 , 333141 , 340087 , 340095 , 340099 , 340147 , 340148 , 341099 , 341256 , 341266 , 342259 , 346755 , 350147 , 350148
• Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, Request filename, Request headers, SOAP request data, XML request data

Vulnerability Description

Open Access Management (OpenAM) is an access management solution. From 13.0.0 until 16.1.2, the OAuth2 authorize endpoint’s display=wap consent page reflects request-derived values through ConsentRequiredResource and wap/authorize.ftl without HTML escaping. An attacker can induce a user with an active OpenAM session to follow a crafted authorization link and execute JavaScript in the OpenAM origin, enabling session or cookie theft, CSRF-token disclosure, and actions with the victim’s privileges. At least one registered OAuth2 client is required, but the attacker does not need to control that client. This issue is fixed in version 16.1.2.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (333140 , 333141 , 340087 , 340095 , 340099 , 340147 , 340148 , 341099 , 341256 , 341266 , 342259 , 346755 , 350147 , 350148 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: OpenIdentityPlatform OpenAM version >= 13.0.0, < 16.1.2.
   • No specific CNA/vendor solution or workaround is included in the current CVE Record (opens in a new tab) . Review the vendor’s security advisories and supported-release guidance before making changes.

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• CVE authority reference: https://github.com/OpenIdentityPlatform/OpenAM/commit/98cee2dfe701c2e16e5bcee34e6fd9d913925118 (opens in a new tab)
• CVE authority reference: https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.2 (opens in a new tab)
• CVE authority reference: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-vqxv-6xrh-49cp (opens in a new tab)

Test or Research Source

• Source: Atomicorp AI Research Framework
• Tags: cve, derived, waf-probe, xss

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .