CVE-2025-7523
BaseFortify
Publication date: 2025-07-13
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jinher | jinher_oa | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-611 | The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. |
| CWE-610 | The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7523 is a critical XML External Entity (XXE) injection vulnerability in Jinhe OA version 1.0, specifically in the /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx endpoint. It occurs because the application processes XML input without properly disabling or validating external entity references. This allows unauthenticated attackers to send specially crafted XML documents containing external entity declarations. When processed by the server, these external entities can lead to unauthorized actions such as reading arbitrary files, conducting server-side request forgery (SSRF), scanning internal networks, and exfiltrating sensitive data via out-of-band techniques. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized disclosure of sensitive files on the server, enabling attackers to read configuration files or other sensitive data. It can also be used to perform SSRF attacks, allowing attackers to scan internal networks or interact with internal services. Additionally, attackers may exfiltrate data out-of-band to their own servers, potentially leading to data breaches. In some cases, it may even allow remote code execution. The vulnerability can be exploited remotely without authentication, making it a significant security risk. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual POST requests to the endpoint /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx containing XML payloads with DOCTYPE declarations referencing external entities. You can use network traffic inspection tools or web server logs to identify such requests. For example, using curl to test the endpoint with a crafted XML payload containing an external entity reference can help verify if the system is vulnerable. Additionally, Google dorking with the query inurl:c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx can help identify exposed instances. Commands to detect suspicious activity include: 1) Using curl to send a test XML payload: curl -X POST -H "Content-Type: application/xml" --data-binary @test_payload.xml http://target/c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx 2) Searching web server logs for POST requests containing "DOCTYPE" or "<!ENTITY" 3) Using network monitoring tools (e.g., tcpdump, Wireshark) to capture outbound HTTP requests that may indicate out-of-band data exfiltration triggered by XXE exploitation. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Disable XML external entity processing in the XML parser configuration (e.g., set XmlResolver to null in .NET environments). 2) Implement strict input validation to reject XML documents containing DOCTYPE declarations or external entity references. 3) Restrict outbound network connections from the server to prevent data exfiltration via out-of-band channels. 4) Consider using alternative data formats such as JSON to avoid XML parsing risks. 5) Deploy Web Application Firewall (WAF) rules to detect and block XXE attack attempts. 6) Apply any available security patches from the vendor or replace the affected component with a secure alternative. 7) Conduct regular security audits and monitor logs for suspicious activity related to this endpoint. [3]