dbcve.org
Jinher OaApplication · Jinher

CVE-2025-7523

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in Jinher OA 1.0 and classified as problematic. Affected by this issue is some unknown functionality of the file /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx. The manipulation leads to xml external entity reference. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A critical XXE (XML External Entity) vulnerability in Jinher OA 1.0 allows remote attackers to inject malicious XML via the /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx endpoint. The vulnerable XML parser processes external entity references, potentially enabling server-side request forgery (SSRF), denial of service, or unauthorized file disclosure.

MitigationDisable external entity processing in the XML parser configuration for the affected DelTemp.aspx page, implement strict input validation for XML uploads, and apply vendor patches if available. As a temporary measure, consider restricting access to this endpoint until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jinher OaApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Jinher OA version 1.0 is installed
    Check the application's about page, version information in the installation directory, or query the application's main API endpoint for version metadata. Look for files like version.info, or check the assembly version in bin/Jhsoft.Web.message.dll if accessible.
    Affected if The installed version is Jinher OA version 1.0 exactly
  2. Verify DelTemp.aspx endpoint exists
    Access the URL path /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx on the server and confirm it returns an HTTP 200 response rather than a 404 or 403 error. Check the web server's directory structure under the c6 virtual application.
    Affected if The DelTemp.aspx file exists and responds to HTTP requests at that path
  3. Test XML parser accepts external entities
    Send a crafted XML request with an XXE payload to the DelTemp.aspx endpoint, such as: <?xml version="1.0"?><!DOCTYPE foo [<!ENTITY xxe SYSTEM "file:///etc/passwd">]><root>&xxe;</root>. Capture the response to see if the parser resolves the external entity.
    Affected if The application returns content from the external entity reference in the response, confirming XXE is enabled
  4. Review application XML parser configuration
    Inspect the web.config file for the c6/Jhsoft.Web.message application or the application's machine.config for XmlSettings. Look for XmlReaderSettings with DtdProcessing set to Parse or Prohibit, and check if EntityHandling is set to ExpandEntities.
    Affected if The XML parser is configured to allow DTD processing or expand external entities without restriction
  5. Check for XXE in HTTP access logs
    Review the web server access logs (IIS logs or equivalent) for POST requests to /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx containing DOCTYPE or ENTITY keywords in the request body.
    Affected if Recent POST requests to DelTemp.aspx contain XML with DOCTYPE declarations or external entity references

A user is affected if they are running Jinher OA version 1.0 with the DelTemp.aspx endpoint exposed and the XML parser configured to process external entities.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable external entity processing in the XML parser configuration for the affected DelTemp.aspx page, implement strict input validation for XML uploads, and apply vendor patches if available. As a temporary measure, consider restricting access to this endpoint until patched.

Fix this in Jinher Oa Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7523 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7523 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data