Skip to main content
CVE-2025-9655VulnerabilityPublished

CVE-2025-9655: O2OA · Cross Site Scripting

Affects O2OASource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
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:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
O2OAAffected
  • =10.0-410
Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Apply strict input validation and output encoding on the 'Description' field within O2OA, if possible through configuration or custom code, to neutralize malicious scripts. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing the platform. 3) Monitor and audit user-generated content for suspicious inputs that could exploit this vulnerability. 4) Educate users about the risks of clicking on unexpected links or interacting with untrusted profile pages within O2OA. 5) Isolate the O2OA deployment within a segmented network zone with limited access to sensitive systems. 6) Regularly check for vendor updates and apply the official patch as soon as it is released. 7) Use web application firewalls (WAFs) with custom rules to detect and block XSS payloads targeting the vulnerable endpoint. These steps go beyond generic advice by focusing on compensating controls until the vendor patch is available.

Description

A weakness has been identified in O2OA up to 10.0-410. This affects an unknown part of the file /x_organization_assemble_control/jaxrs/person/ of the component Personal Profile Page. Executing manipulation of the argument Description can lead to cross site scripting. The attack can be launched remotely. The vendor replied in the GitHub issue (translated from simplified Chinese): "This issue will be fixed in the new version."

References

Community reviews

Loading reviews…