CVE-2025-11341
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 security flaw has been discovered in Jinher OA up to 2.0. This affects an unknown function of the file /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx/?type=SystemUserInfo&style=1. Performing manipulation results in xml external entity reference. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited.
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 confidenceJinher OA versions up to 2.0 contain an XML External Entity (XXE) injection vulnerability in the WebDesign.aspx endpoint (/c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx/). An attacker can craft malicious XML documents that reference external entities, potentially exposing sensitive server files, performing SSRF attacks against internal infrastructure, or causing denial of service. The vulnerability is remotely exploitable without authentication.
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<= 2.0CVSS 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 installationIdentify the web server hosting Jinher OA by checking web server logs, installed applications, or by accessing the application's main page. Look for Jinher OA-specific files or directories in the web root.Affected if Jinher OA is installed on the server
-
Check Jinher OA versionLocate version information in the application installation directory, typically found in version.txt, about.txt, or assembly version metadata within the bin directory. Alternatively, check the HTTP server banner or error pages that may reveal version details.Affected if The installed version is 2.0 or below
-
Verify vulnerable endpoint existsAttempt to access the URL path /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx on the target server using a GET request. A 200 or 404 response (rather than 404) indicates the endpoint exists.Affected if The WebDesign.aspx endpoint is accessible and responds to requests
-
Confirm XML upload functionalitySend a POST request to the WebDesign.aspx endpoint with a Content-Type of application/xml or text/xml containing a simple XML payload. Check if the endpoint accepts and processes XML input.Affected if The endpoint accepts and processes XML requests without rejecting them
-
Check for XXE vulnerability indicatorsSend a crafted XXE test payload to the endpoint (for example, an XML document with an external entity referencing a local file or internal URL) and observe the response for data exfiltration or error messages revealing entity expansion.Affected if The endpoint processes external entities and returns content from internal resources or displays XXE-related error messages
A user is affected if Jinher OA version 2.0 or below is installed and the WebDesign.aspx endpoint is accessible, as this endpoint accepts XML input that can be exploited for XXE injection.
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 used by the WebDesign.aspx component, implement strict input validation for XML uploads, and apply any available vendor patches. As an interim measure, deploy WAF rules to detect and block XXE attack patterns.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11341 — 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-11341 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