Executive Summary

CVE-2025-10092 is a critical XML External Entity (XXE) vulnerability in Jinher OA up to version 1.2. It exists in an XML handler component at the endpoint /c6/Jhsoft.Web.projectmanage/TaskManage/AddTask.aspx/?Type=add. The vulnerability allows attackers to manipulate XML input to include external entity references, which the server processes improperly. This can lead to unauthorized disclosure of sensitive data, as the server may read and expose local files or other resources. The attack can be performed remotely without authentication, making it easy to exploit. The flaw arises because the XML parser does not disable external entity resolution, enabling attackers to craft malicious XML payloads that cause the server to fetch and disclose data or perform other malicious actions. [1, 2, 3]

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can have serious impacts including unauthorized reading of sensitive server files (e.g., system configuration files), server-side request forgery (SSRF) attacks, internal network scanning, and potentially remote code execution. Attackers can exfiltrate confidential data by causing the server to send file contents to attacker-controlled servers. The vulnerability affects confidentiality, integrity, and availability of the system, potentially leading to data breaches and disruption of system operations. [1, 2]

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by sending specially crafted XML payloads containing external entity references to the vulnerable endpoint `/c6/Jhsoft.Web.projectmanage/TaskManage/AddTask.aspx/?Type=add` and observing the server's behavior or network traffic for out-of-band data exfiltration attempts. For detection, you can use tools like curl or custom scripts to POST XML payloads with DOCTYPE declarations referencing external entities. Example detection payloads include sending an XML with a SYSTEM entity pointing to an attacker-controlled server to see if the server makes outbound requests. Commands might look like: `curl -X POST -H "Content-Type: application/xml" --data-binary @payload.xml http://target/c6/Jhsoft.Web.projectmanage/TaskManage/AddTask.aspx/?Type=add` where `payload.xml` contains the malicious XML. Monitoring outbound HTTP requests from the server to attacker-controlled domains can also indicate exploitation attempts. [2]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include disabling XML External Entity (XXE) processing in the XML parser used by the application (e.g., setting XmlResolver to null in .NET), implementing strict input validation to reject XML documents containing DOCTYPE declarations or external entities, and restricting outbound network connections from the server to prevent data exfiltration (egress filtering). Additionally, consider deploying Web Application Firewall (WAF) rules to detect and block XXE attack attempts, applying any available security patches from the vendor, and if possible, replacing the affected product or using alternative data formats such as JSON instead of XML. [2]

Useful 0 Not Useful 0