Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-9680: Cross Site Scripting in O2OA

0
Medium
VulnerabilityCVE-2025-9680cvecve-2025-9680
Published: Sat Aug 30 2025 (08/30/2025, 07:02:06 UTC)
Source: CVE Database V5
Product: O2OA

Description

A vulnerability was detected in O2OA up to 10.0-410. This impacts an unknown function of the file /x_portal_assemble_designer/jaxrs/page of the component Personal Profile Page. Performing manipulation results in cross site scripting. The attack can be initiated remotely. The exploit is now public and may be used. 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: 09/07/2025, 00:37:11 UTC

Technical Analysis

CVE-2025-9680 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 function within the /x_portal_assemble_designer/jaxrs/page endpoint of the Personal Profile Page component. This flaw allows an attacker to inject malicious scripts that execute in the context of a victim's browser when they access a crafted page or input. The attack can be initiated remotely without authentication, requiring only user interaction to trigger the malicious payload. The vulnerability has a CVSS 4.0 base score of 5.1, indicating a medium severity level. The vector details show that the attack is network accessible (AV:N), requires low attack complexity (AC:L), no privileges (PR:L) but does require user interaction (UI:P). The impact is primarily on confidentiality and integrity, with limited impact on availability. The vendor has acknowledged the issue and indicated that a fix will be included in a future release, but as of the publication date, no patch is available. Public exploit code has been released, increasing the risk of exploitation. The vulnerability could be leveraged to steal session cookies, perform actions on behalf of users, or deliver further malware, especially targeting users with elevated privileges within O2OA. Given the nature of O2OA as an enterprise collaboration and office automation platform, exploitation could lead to unauthorized access to sensitive organizational data and disruption of business processes.

Potential Impact

For European organizations using O2OA, this vulnerability poses a significant risk to user data confidentiality and integrity. Attackers exploiting this XSS flaw could hijack user sessions, steal credentials, or manipulate user interactions, potentially leading to unauthorized access to internal communications, documents, and personal information. This is particularly concerning for sectors handling sensitive data such as finance, healthcare, and government agencies. The remote and unauthenticated nature of the attack vector increases the likelihood of exploitation, especially in environments where users may be less aware of phishing or social engineering tactics. Additionally, the public availability of exploit code lowers the barrier for attackers, increasing the threat landscape. The lack of an immediate patch means organizations must rely on interim mitigations, which may not fully prevent exploitation. This vulnerability could also be used as a foothold for further attacks within the network, impacting operational continuity and compliance with data protection regulations such as GDPR.

Mitigation Recommendations

European organizations should implement the following specific measures: 1) Immediately restrict access to the affected /x_portal_assemble_designer/jaxrs/page endpoint using web application firewalls (WAFs) or reverse proxies with custom rules to detect and block suspicious input patterns indicative of XSS attempts. 2) Enforce strict Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 3) Conduct thorough input validation and output encoding on all user-supplied data within the O2OA platform, especially in the Personal Profile Page component, if customizations or extensions are in place. 4) Educate users on the risks of clicking unknown links or interacting with untrusted content within the platform. 5) Monitor logs and network traffic for unusual activity related to the vulnerable endpoint. 6) Plan and prioritize upgrading to the vendor’s patched version once released. 7) Consider isolating or segmenting the O2OA environment to limit lateral movement in case of compromise. 8) Regularly review and update incident response plans to include scenarios involving XSS exploitation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-08-29T10:49:31.149Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68b2a5a1ad5a09ad007ff3b2

Added to database: 8/30/2025, 7:17:53 AM

Last enriched: 9/7/2025, 12:37:11 AM

Last updated: 10/14/2025, 11:41:42 PM

Views: 55

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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