Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInject crafted JavaScript into Web UI (PR:N)
-
DeliveryLure authenticated operator to view page (UI:R)
-
ExploitTrigger XSS in trusted session (S:C)
-
ExecutionExecute script in victim browser context
-
ImpactExfiltrate session credentials (C:H)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a victim with an active, trusted session in the Security Verify Access / Verify Identity Access Web UI view the attacker-supplied content (UI:R) - typically an authenticated administrator or operator, which limits exploitation to successful lure/phishing or injection into a page the victim already visits. The injection itself needs no authentication (PR:N), but the payload only yields value (credential/session disclosure) once an authenticated user renders it, so the practical limiting factors are the required user interaction and the presence of an active privileged session. The input CVSS marks AV:L, which would imply local access rather than remote web delivery; defenders should confirm with IBM whether the UI is reachable only locally/over a management network, as this materially changes exposure. |
| Impact | This is a stored/reflected cross-site scripting flaw (CWE-79) in the Web UI of IBM Security Verify Access / Verify Identity Access, with an IBM-assigned CVSS 3.1 base score of 8.2 driven largely by a changed scope (S:C) and high confidentiality/integrity impact. The signals conflict in one important way: the vector specifies AV:L (local attack vector), yet the description and the XSS nature (an unauthenticated user embedding JavaScript into a web UI that then executes in a victim's trusted session) point to network-reachable, browser-delivered exploitation - the AV:L rating is unusual for web XSS and should be verified with IBM before treating this as local-only. PR:N confirms no authentication is required to plant the payload, but UI:R means a victim (likely an authenticated operator/admin) must view the malicious content, which lowers real-world exploitability versus a no-interaction bug. There is no EPSS score, no CISA KEV listing, and no public exploit referenced, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the score is high but the practical risk is moderated by the user-interaction requirement and the targeted (phishing/lure) nature of XSS. A patch is available from IBM, making remediation straightforward. Net: a legitimate priority for internet-exposed or operator-facing deployments of these IAM appliances because of the credential/session-disclosure impact, but not a mass-exploitation emergency absent POC or KEV data. |
| Exploit ScenarioDerived | An unauthenticated attacker crafts a request or input that injects arbitrary JavaScript into the Security Verify Access Web UI, then lures an authenticated administrator or user into viewing the affected page. When the victim loads it, the script runs in their trusted session and can steal session tokens or credentials, enabling account takeover of the IAM console. No public proof-of-concept is referenced, and exploitation depends on the victim interacting with the malicious content (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Cross-site scripting (CWE-79) in the Web UI of IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 - including their container editions - lets an attacker inject arbitrary JavaScript into pages rendered by the interface, which can execute in the browser of an authenticated administrator or operator with an active trusted session and potentially disclose credentials or session data. The injection itself requires no authentication (the supplied vector is PR:N), but the payload is only harmful when a victim loads the crafted content (UI:R), so exploitation depends on a successful lure, a poisoned page, or injection into a view the victim already opens. IBM rates this 8.2 (scope changed, high confidentiality and integrity impact); no public exploit code or active exploitation has been identified at time of analysis, though the faulted UI is a high-value administrative target. Note a vector discrepancy: the published CVSS marks AV:L whereas the independent assessment scores AV:N, so defenders should confirm with IBM whether the affected UI is reachable remotely or only from a local/management network, since that materially changes exposure.
RemediationAI
IBM has published a fix; consult the vendor advisory at https://www.ibm.com/support/pages/node/7291628 for the exact patched build applicable to your release train and upgrade Security Verify Access 10.0.x (through 10.0.9.2) and Verify Identity Access 11.0.x (through 11.0.3), including the corresponding container images, to that level - the input data confirms patch availability from IBM but does not enumerate a specific fix version, so the advisory is the authoritative source. Until patching is complete, reduce the attack surface of the administrative UI: restrict the management console to trusted management networks or an administrative jump host (a compensating control that also aligns with the AV:L interpretation of the published vector, but which offers no protection if the UI is genuinely internet-reachable per the AV:N assessment), deploy a strict Content-Security-Policy on the console to blunt inline script execution (effective only against CSP-compatible payloads and requires testing so it does not break UI functionality), and set session cookies with HttpOnly and Secure flags so stolen cookies cannot be read or replayed over plaintext (this limits but does not prevent same-session credential capture). Because the payload is dangerous when rendered inside an authenticated session, enforce phishing-resistant MFA and short session/idle timeouts for console users, and consider terminating active administrative sessions after applying the patch in case credentials were already exposed. There is no vendor-released patch identified beyond the advisory reference, and no public exploit code has been observed, so prioritization should follow standard administrative-interface risk treatment rather than emergency response.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 4 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-79 cross-site scripting weakness in the web-based management interface shared by IBM Security Verify Access (the successor to IBM Security Access Manager) and IBM Verify Identity Access, the federation/SSO and identity-governance product line. Because the injected script executes inside the origin of the management console, it inherits the victim's authenticated context; the CVSS scope change (S:C) reflects that compromise of the browser context can affect resources beyond the vulnerable component itself, such as credential material or downstream sessions. The CPE entries cover four distinct build channels - security_verify_access, verify_identity_access, and both containerized variants (security_verify_access_container, verify_identity_access_container) - meaning on-premises appliances and container images share the same vulnerable UI code path. Input that is not properly neutralized before being reflected or stored into the Web UI is the likely root cause; the practical consequence is script execution in a privileged administrative session, enabling credential disclosure or unauthorized actions within the trusted session.
Know when Security Verify Access gets its next vulnerability
- 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
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Web-UI XSS is browser-delivered so AV:N (contradicting input AV:L); PR:N since injection is unauthenticated, UI:R as a victim must render it, S:C for cross-context execution, C:H for credential disclosure, I:L for UI alteration.
Primary rating from Vendor (ibm).
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session
Executive ViewAI
A cross-site scripting flaw in the web management console of IBM Security Verify Access (versions 10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container editions, could allow an attacker to run malicious script in the browsers of the administrators and operators who manage the organization's identity and access infrastructure. Because that console controls authentication, authorization, and access policy for the enterprise, theft of an administrator's session or credentials could cascade into broad downstream compromise of protected applications and data. IBM has made a fix available, making this a prioritized scheduled remediation rather than an active emergency.
Apply vendor patch.
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.
More in Security Verify Access
View allIBM Security Verify Access 10.0.0 through 10.0.8 OIDC Provider could allow a remote authenticated attacker to conduct ph
IBM Security Verify Access 10.0.0 through 10.0.7 and IBM Application Gateway 20.01 through 24.03 could allow a remote at
Unauthenticated remote code execution affects IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity A
Remote code execution is achievable in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 1
An out-of-bounds write in IBM Verify Identity Access (and its predecessor branding, IBM Security Verify Access, plus bot
IBM Security Verify Access Appliance 10.0.0 through 10.0.8 contains hard-coded credentials, such as a password or crypto
IBM Security Verify Access Appliance 10.0.0 through 10.0.8 contains hard-coded credentials, such as a password or crypto
IBM Security Access Manager 9.0.7 and IBM Security Verify Access 10.0.0 could allow an unauthorized public Oauth client
IBM Verify Identity Access (formerly IBM Security Verify Access) in container and appliance deployments can silently fai
Remote code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.
Arbitrary command execution in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 thro
Authenticated argument injection in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0
EUVD-2026-95279
GHSA-48x7-jwrr-pjcx
NVD
CVE.org
EPSS
Exploit-DB