CVE-2025-9717: O2OA · Cross-site Scripting
Affects O2OASource CVE Database V5
Public exploit available · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 31 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| O2OA | Affected
| Fixed in– |
AI-suggested
- Immediate patching: Organizations should monitor O2OA vendor communications for official patches or updates addressing CVE-2025-9717 and apply them promptly.
- Input validation and sanitization: Until patches are available, implement web application firewall (WAF) rules to detect and block suspicious payloads targeting the vulnerable parameters (name, shortName, distinguishedName, pinyin, pinyinInitial, levelName).
- Content Security Policy (CSP): Deploy strict CSP headers to restrict the execution of unauthorized scripts in browsers, mitigating the impact of XSS attacks.
- User awareness: Educate users about the risks of clicking on suspicious links and encourage cautious behavior to reduce the likelihood of successful exploitation.
- Logging and monitoring: Enhance logging of web application inputs and monitor for unusual activities or repeated attempts to exploit these parameters.
- Review and harden authentication mechanisms: Since the vulnerability requires no authentication but user interaction, strengthening multi-factor authentication and session management can limit attacker leverage post-exploitation.
- Conduct security testing: Perform penetration testing and code reviews focusing on input handling in the affected component to identify and remediate similar issues proactively.
Description
A vulnerability was identified in O2OA up to 10.0-410. Affected by this issue is some unknown functionality of the file /x_organization_assemble_control/jaxrs/unit/ of the component Personal Profile Page. Such manipulation of the argument name/shortName/distinguishedName/pinyin/pinyinInitial/levelName leads to cross site scripting. The attack may be launched remotely. The exploit is publicly available and might be used.