Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V3 - Web Frontend Security HttpOnly cookie flag
|
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 15, 2026
OpenAM Community Edition through 16.0.6 ships its iPlanetDirectoryPro SSO session cookie with HttpOnly disabled and no SameSite attribute by default, and reuses that same cookie value as the CSRF token for the OAuth/OIDC consent flow. When chained with any other same-origin XSS in the OpenAM console, a single clicked attacker link lets a remote, unauthenticated attacker read the cookie from document.cookie, hijack a logged-in console user's full SSO session, and simultaneously submit attacker-controlled OAuth consent grants using the stolen cookie as the anti-CSRF token. The issue is fixed by
Earlier versions of this analysis (1)
Session theft and unauthorized OAuth consent grant in OpenAM Community Edition through 16.0.6 result from the default configuration issuing the iPlanetDirectoryPro SSO cookie with HttpOnly=false and simultaneously reusing that cookie as the CSRF token in OAuth/OIDC consent flows. An authenticated console user who clicks a single attacker-crafted link, when chained with any co-resident same-origin XSS on the OpenAM origin, loses their SSO session and simultaneously completes an attacker-driven OAuth consent grant in one interaction. No public exploit code has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog, but the dual-purpose misuse of the session cookie - as both a bearer token and a CSRF guard - substantially amplifies the impact of any XSS present in the same origin.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Network vector, high complexity (requires chaining with same-origin XSS), no attacker privileges needed, user interaction required, scope changed via OAuth grants, high confidentiality and integrity impact from session and consent hijack.
Primary rating from Vendor (https://github.com/OpenIdentityPlatform/OpenAM).
CVSS VectorVendor: https://github.com/OpenIdentityPlatform/OpenAM
Lifecycle Timeline
3DescriptionCVE.org
Summary
Description An Insecure Default Initialization of Resource (CWE-1188) issue in the OpenAM default configuration ships the iPlanetDirectoryPro SSO cookie with HttpOnly=false. Also, the iPlanetDirectoryPro SSO cookie is used as a CSRF token in OAuth/OIDC flows. This affects OpenAM Community Edition through version 16.0.6 and was patched in version 16.1.1.
Impact
A single click on an attacker link may yield full SSO session theft of any authenticated console user when chained with any other same-origin XSS in the OpenAM origin. The missing SameSite default also widens the CSRF surface. Also, because the consent flow reuses the SSO cookie as its CSRF token, any XSS in the OpenAM origin both steals the session and completes attacker-driven OAuth consent grants in one step.
Patch
This has been patched in OpenAM Community Edition version 16.1.1. Users are encouraged to update to the latest release.
Blast Radius
ecosystem impact- 55 maven packages depend on org.openidentityplatform.openam:openam-core (51 direct, 4 indirect)
Ecosystem-wide dependent count for version 16.1.1.
Executive ViewAI
OpenAM Community Edition version 16.0.6 and earlier contains a critical configuration flaw that allows attackers to hijack administrative sessions and grant unauthorized OAuth access through a single user interaction, contingent on the presence of cross-site scripting (XSS) on the same domain. While no public exploit has been identified at time of analysis, the vulnerability carries inherent risk and should not be dismissed as theoretical. Organizations should prioritize immediate inventory, assessment, and mitigation planning for OpenAM deployments until vendor patches become available.
Within 24 hours, conduct a complete inventory of OpenAM Community Edition deployments running version 16.0.6 or earlier and identify all co-resident applications on the same origin that may introduce XSS vectors. Within 7 days, implement interim hardening measures including enabling HttpOnly on the iPlanetDirectoryPro session cookie (if application support permits), deploying XSS-focused Web Application Firewall rules, and evaluating the feasibility of segregating CSRF token generation from session cookies. Within 30 days, contact ForgeRock to confirm patch availability timelines, execute an upgrade to a patched version if available, or develop a longer-term mitigation strategy such as network isolation or platform migration if no remediation timeline is provided.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) enabling HttpOnly flag on the iPlanetDirectoryPro session cookie if supported by your deployment; (2) implementing strict input validation and output encoding across all web applications on the same domain to prevent XSS; (3) deploying Web Application Firewall rules to detect and block consent flow manipulation; (4) segregating CSRF token generation from the session cookie mechanism where architecturally feasible; (5) restricting OAuth scopes available during consent flows to limit potential damage if unauthorized grants occur.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
EUVD-2026-78353
GHSA-fpmh-vx4h-xc33
NVD
CVE.org
EPSS
Exploit-DB