Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Redirection and Modification
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The affected product accepts user-supplied input within a URL parameter without enforcing expected sanitization or encoding before rendering it within the response. This condition allows for the injection of malicious JavaScript payloads. An attacker can leverage this vulnerability to cause the user's browser to redirect to a malicious website, modify the user interface of the webpage, or retrieve sensitive information from the browser. However, the impact is mitigated for session hijacking as all session-related sensitive cookies are protected by the httpOnly flag.
- Published
- Jul 20, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-79
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · WSO2
- 6.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api control plane | cpe:2.3:a:wso2:api_control_plane |
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | identity server | cpe:2.3:a:wso2:identity_server |
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api control plane4.5.0 and later · before 4.5.0.56
- wso2 api control plane4.6.0 and later · before 4.6.0.20
- wso2 api manager4.2.0 and later · before 4.2.0.195
- wso2 api manager4.3.0 and later · before 4.3.0.106
- wso2 api manager4.4.0 and later · before 4.4.0.70
- wso2 api manager4.5.0 and later · before 4.5.0.55
- wso2 api manager4.6.0 and later · before 4.6.0.19
- wso2 identity server6.0.0 and later · before 6.0.0.263
- wso2 identity server6.1.0 and later · before 6.1.0.266
- wso2 identity server7.0.0 and later · before 7.0.0.144
- wso2 identity server7.1.0 and later · before 7.1.0.53
- wso2 identity server7.2.0 and later · before 7.2.0.12
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.
WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.56affected
- 4.6.0 and later · before 4.6.0.20affected
WSO2 WSO2 API Manager
- 4.2.0 and later · before 4.2.0.195affected
- 4.3.0 and later · before 4.3.0.106affected
- 4.4.0 and later · before 4.4.0.70affected
- 4.5.0 and later · before 4.5.0.55affected
- 4.6.0 and later · before 4.6.0.19affected
WSO2 WSO2 Identity Server
- 6.0.0 and later · before 6.0.0.263affected
- 6.1.0 and later · before 6.1.0.266affected
- 7.0.0 and later · before 7.0.0.144affected
- 7.1.0 and later · before 7.1.0.53affected
- 7.2.0 and later · before 7.2.0.12affected
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV70This week
- CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover39Monitor
- CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-4249Jul 6, 2026 · Denial of Service via Malicious JSON Payloads in Throttling Events in Multiple WSO2 Products Causing Persistent Service Disruption34Monitor
- ← EarlierCVE-2025-8591Jul 6, 2026 · Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Modification24Monitor
- Later →CVE-2024-10302Aug 6, 2026 · Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Maneesha Dewminereporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-859114 days apartReflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Modification24Monitor
- CVE-2025-10853257 days apartReflected Cross-Site Scripting (XSS) in Management Console of Multiple WSO2 Products Due to Improper Output Encoding24Monitor
- CVE-2025-5770257 days apartReflected Cross-Site Scripting (XSS) in Authentication Endpoints of Multiple WSO2 Products24Monitor
- CVE-2025-5350269 days apartSSRF and Reflected XSS Vulnerability in Deprecated Try-It Feature of Multiple WSO2 Products19Monitor
- CVE-2025-4760300 days apartAuthenticated Stored Cross-Site Scripting (XSS) in Multiple WSO2 Products via API Document Upload in Publisher19Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.