Executive Summary

CVE-2025-9736 is a stored cross-site scripting (XSS) vulnerability in the O2OA application (up to version 10.0-410), specifically in the Personal Profile Page component at the endpoint /x_query_assemble_designer/jaxrs/statement. It occurs because user inputs in fields like description or queryName are not properly sanitized before being stored and later rendered. This allows attackers to inject malicious JavaScript code that executes in other users' browsers when they view the affected data, potentially compromising user sessions and data integrity. [1, 2, 3]

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows attackers to execute persistent malicious JavaScript code in the browsers of users who view the affected profile or data. The impact includes theft of session tokens or sensitive information, unauthorized actions performed on behalf of authenticated users, and compromise of data integrity. The attack can be launched remotely and requires some user interaction to trigger the script execution. [1, 2, 3]

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by monitoring and analyzing HTTP POST requests to the endpoint `/x_query_assemble_designer/jaxrs/statement` for suspicious payloads containing script tags or event handlers such as `<img src=1 onerror=alert(1)>`. You can use tools like curl or wget to send crafted requests to test the endpoint. Additionally, inspecting logs for unusual input in the `description`, `applicationName`, or `queryName` fields may help detect exploitation attempts. Example command to test the endpoint with a malicious payload using curl: curl -X POST https://<target>/x_query_assemble_designer/jaxrs/statement -H "Content-Type: application/json" -d '{"description":"<img src=1 onerror=alert(1)>","queryName":"test"}' [2]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include restricting access to the vulnerable endpoint, applying input filtering and output encoding to sanitize user inputs, and monitoring for exploitation attempts. Since no official patch is currently available, consider replacing or disabling the affected component until the vendor releases a fixed version. Additionally, educate users to be cautious of unexpected profile data and consider implementing web application firewalls (WAF) rules to block malicious payloads targeting this vulnerability. [2, 3]

Useful 0 Not Useful 0