Skip to main content

CVE-2025-9716: Cross Site Scripting in O2OA

Medium
VulnerabilityCVE-2025-9716cvecve-2025-9716
Published: Sun Aug 31 2025 (08/31/2025, 04:32:05 UTC)
Source: CVE Database V5
Product: O2OA

Description

A vulnerability was determined in O2OA up to 10.0-410. Affected by this vulnerability is an unknown functionality of the file /x_processplatform_assemble_designer/jaxrs/form of the component Personal Profile Page. This manipulation of the argument name/alias/description causes cross site scripting. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor replied in the GitHub issue (translated from simplified Chinese): "This issue will be fixed in the new version."

AI-Powered Analysis

AILast updated: 08/31/2025, 05:02:46 UTC

Technical Analysis

CVE-2025-9716 is a cross-site scripting (XSS) vulnerability identified in the O2OA platform, specifically affecting versions up to 10.0-410. The vulnerability resides in an unspecified functionality within the file /x_processplatform_assemble_designer/jaxrs/form, which is part of the Personal Profile Page component. The issue arises from improper sanitization or validation of user-supplied input in the parameters name, alias, or description, allowing an attacker to inject malicious scripts. This vulnerability can be exploited remotely without requiring authentication, although it does require some user interaction (e.g., a victim visiting a crafted URL or page). The CVSS 4.0 base score is 5.1, indicating a medium severity level. The attack vector is network-based with low attack complexity and no privileges required, but user interaction is necessary. The impact primarily affects the confidentiality and integrity of user data, with limited impact on availability. The vendor has acknowledged the issue publicly on GitHub and plans to fix it in a future release, but no patch is currently available. While no known exploits in the wild have been reported, the vulnerability has been publicly disclosed, increasing the risk of exploitation by attackers. XSS vulnerabilities like this can be leveraged for session hijacking, phishing, or delivering further malicious payloads, potentially compromising user accounts and sensitive information within the O2OA platform.

Potential Impact

For European organizations using O2OA, this vulnerability poses a moderate risk. O2OA is a collaborative office automation platform, often used for internal communication, document management, and workflow automation. Exploitation of this XSS flaw could allow attackers to execute arbitrary scripts in the context of authenticated users, leading to session hijacking, theft of sensitive data, or unauthorized actions within the platform. This can result in data breaches, loss of user trust, and potential compliance violations under GDPR if personal data is exposed. The remote exploitability without authentication increases the threat surface, especially in organizations with internet-facing O2OA instances. However, the requirement for user interaction somewhat limits automated mass exploitation. The absence of a current patch means organizations must rely on interim mitigations. Given the collaborative nature of O2OA, successful exploitation could facilitate lateral movement or privilege escalation within an enterprise environment, amplifying the impact.

Mitigation Recommendations

European organizations should implement several targeted mitigations: 1) Apply strict input validation and output encoding on all user-supplied data fields, especially name, alias, and description parameters, to neutralize malicious scripts. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 3) Restrict access to the vulnerable Personal Profile Page component to trusted users or internal networks until a patch is available. 4) Monitor web server logs and application behavior for unusual requests targeting the /x_processplatform_assemble_designer/jaxrs/form endpoint, indicating potential exploitation attempts. 5) Educate users about phishing and suspicious links to reduce the risk of user interaction with malicious payloads. 6) Maintain up-to-date backups and incident response plans to quickly recover from potential compromises. 7) Track vendor updates closely and prioritize patching as soon as the fix is released. 8) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-08-30T11:05:20.083Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68b3d3f0ad5a09ad00b081ea

Added to database: 8/31/2025, 4:47:44 AM

Last enriched: 8/31/2025, 5:02:46 AM

Last updated: 9/1/2025, 12:34:18 AM

Views: 9

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats