CVE-2025-10091
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 · uneditedA vulnerability has been found in Jinher OA up to 1.2. This affects an unknown function of the file /c6/Jhsoft.Web.projectmanage/ProjectManage/XmlHttp.aspx/?Type=add of the component XML Handler. The manipulation leads to xml external entity reference. Remote exploitation of the attack is possible. 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 confidenceThis is an XML External Entity (XXE) injection vulnerability in Jinher OA's XML handler component at /c6/Jhsoft.Web.projectmanage/ProjectManage/XmlHttp.aspx. The endpoint processes XML input without disabling external entity references, allowing remote attackers to inject malicious XML to read internal files, perform SSRF attacks, or cause denial of service.
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<= 1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Jinher OA installation and versionLocate the Jinher OA installation directory and check the version information, typically found in version files, assembly info, or the application header/about page. Compare the installed version against the affected range (<= 1.2).Affected if The installed version is 1.2 or lower.
-
Locate the vulnerable XML handler endpointCheck if the file XmlHttp.aspx exists under the path /c6/Jhsoft.Web.projectmanage/ProjectManage/ in the web root directory of the Jinher OA installation.Affected if The file /c6/Jhsoft.Web.projectmanage/ProjectManage/XmlHttp.aspx exists and is accessible via HTTP/HTTPS.
-
Verify XML handler is accessible and functionalSend a test HTTP request (GET or POST) to the XmlHttp.aspx endpoint and confirm it responds. Check the HTTP response code and whether the page accepts XML input.Affected if The endpoint responds with HTTP 200 and accepts XML input without authentication errors.
-
Check XML parser configuration for external entity settingsExamine the XmlHttp.aspx code or the associated web.config/application configuration files to determine if the XML parser has external entity processing disabled (look for settings such as DTDProcessing, XmlResolver, or entity resolution disabled).Affected if The XML parser configuration does NOT explicitly disable external entity processing (DTD processing is enabled, or XmlResolver is not set to null).
A user is affected if they are running Jinher OA version 1.2 or lower with the XmlHttp.aspx endpoint exposed and the XML parser configured to allow external entity processing.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable external entity processing in the XML parser configuration for the affected XmlHttp.aspx handler, or apply any available vendor patch for Jinher OA version 1.2.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10091 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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