CVE-2025-7823
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 was found in Jinher OA 1.2. It has been declared as problematic. This vulnerability affects unknown code of the file ProjectScheduleDelete.aspx. The manipulation leads to xml external entity reference. The attack can be initiated 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 · moderate confidenceA critical XML External Entity (XXE) vulnerability exists in Jinher OA version 1.2 within the ProjectScheduleDelete.aspx file. The vulnerability allows remote attackers to exploit improper XML parsing configuration, potentially leading to disclosure of internal files, denial of service, or server-side request forgery (SSRF).
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.
-
Identify installed Jinher OA versionCheck the application version information in the system configuration, about page, or version file. This is typically found in the application's installation directory or admin panel.Affected if Version is 1.2 exactly (Jinher OA version 1.2)
-
Locate ProjectScheduleDelete.aspx fileSearch for the file 'ProjectScheduleDelete.aspx' in the web root directory or application path. Common paths may include /oa/, /internal/, or the main web application directory.Affected if The file exists in the deployed application
-
Examine XML parser configuration in the affected fileOpen ProjectScheduleDelete.aspx in a text editor and inspect the XML parsing code. Look for XmlDocument, XmlReader, or similar XML processing objects and their configuration settings.Affected if The XML parser is configured without disabling DTD processing or external entity resolution (e.g., no XMLResolver set to null, no DTD processing disabled)
-
Check for XXE vulnerability via test requestIf authorized and in a non-production environment, send a crafted XML request with an external entity reference to ProjectScheduleDelete.aspx and observe if the parser resolves it (e.g., attempts to access internal file paths or external URLs)Affected if The application processes external entities in XML input, indicating XXE is exploitable
You are affected if Jinher OA version 1.2 is deployed AND the ProjectScheduleDelete.aspx file exists with XML parsing that does not explicitly disable 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 XML external entity processing in the ProjectScheduleDelete.aspx XML parser configuration. Implement strict input validation and use secure XML parser settings that disable DTD processing and external entity resolution.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7823 — 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-7823 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