CVE-2025-9669
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 1.0. This issue affects some unknown processing of the file GetTreeDate.aspx. The manipulation of the argument ID leads to sql injection. 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 · moderate confidenceSQL injection vulnerability in Jinher OA 1.0's GetTreeDate.aspx page. The ID parameter is not properly sanitized, allowing attackers to inject malicious SQL queries. This is a critical remote code execution-capable flaw given the CVSS 9.8 score.
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.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 installationSearch for Jinher OA web application files in the web root directory, typically found under IIS web roots or /inetpub/wwwroot/. Look for common Jinher OA directories or check the application's title page for 'Jinher OA' branding.Affected if Jinher OA version 1.0 is installed on the server
-
Locate GetTreeDate.aspxSearch for the file GetTreeDate.aspx within the Jinher OA web application directory structure. Common paths may include /OA/, /office/, or the root web folder.Affected if The file GetTreeDate.aspx exists in the Jinher OA installation
-
Verify the ID parameter is acceptedAttempt to access GetTreeDate.aspx with a test ID parameter (e.g., GetTreeDate.aspx?ID=1). Check if the page accepts the parameter and returns a response rather than rejecting it.Affected if The page accepts the ID parameter without sanitization or error handling
-
Confirm version is 1.0Check the assembly information, version file, or about page within Jinher OA to determine the exact installed version. Version information may be stored in web.config, version.txt, or the application metadata.Affected if The installed version is exactly 1.0 (no patches applied)
If Jinher OA version 1.0 is running with the GetTreeDate.aspx page accessible and the ID parameter is accepted, the environment is affected by this SQL injection vulnerability.
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 dataImplement parameterized queries or prepared statements for the ID parameter in GetTreeDate.aspx. Additionally, apply input validation and consider deploying a WAF as a defensive layer.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9669 — 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-9669 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