CVE-2025-3009
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 classified as critical was found in Jinher Network OA C6. Affected by this vulnerability is an unknown functionality of the file /C6/JHSoft.Web.NetDisk/NetDiskProperty.aspx. The manipulation of the argument ID leads to sql injection. The attack can 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 · moderate confidenceSQL injection vulnerability in Jinher Network OA C6 at /C6/JHSoft.Web.NetDisk/NetDiskProperty.aspx. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. Public exploits are available.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 Network OA C6 installationIdentify the Jinher Network OA C6 installation by checking web server banners, application metadata, or by accessing the application login page and reviewing the source code for vendor strings 'Jinher' or 'JHSoft'.Affected if The system is running Jinher Network OA C6 software.
-
Verify vulnerable endpoint existsAttempt to access the URL path /C6/JHSoft.Web.NetDisk/NetDiskProperty.aspx on the target web server. This may require authentication depending on the version and configuration.Affected if The endpoint returns a valid HTTP response (200 or 302) rather than a 404 error, indicating the NetDiskProperty.aspx module is present.
-
Check if ID parameter accepts inputSend a request to NetDiskProperty.aspx with a test ID parameter value (such as ID=1) and observe whether the application processes it. Review the HTTP response for database-related errors or unexpected behavior.Affected if The ID parameter is accepted and processed by the application without proper validation or parameterization.
-
Inspect web application logs for SQL injection attemptsReview web server logs (IIS, Apache, or application logs) for requests to NetDiskProperty.aspx containing SQL meta-characters in the ID parameter (such as quotes, UNION, SELECT, OR 1=1). Also check for database error messages in responses.Affected if Log analysis reveals SQL injection payloads in the ID parameter or SQL error messages returned by the application.
A system is affected if it runs Jinher Network OA C6 with the NetDiskProperty.aspx endpoint accessible and the ID parameter accepts unsanitized input, allowing SQL 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 dataImplement parameterized queries or prepared statements for the ID parameter. Apply input validation and output encoding. If available, apply vendor patch; otherwise, conduct code review of similar parameters across the application.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3009 — 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-3009 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