CVE-2025-15424
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 Yonyou KSOA 9.0. The affected element is an unknown function of the file /worksheet/agent_worksdel.jsp of the component HTTP GET Parameter Handler. Performing a manipulation of the argument ID results in sql injection. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA SQL injection vulnerability exists in Yonyou KSOA 9.0 within the /workshop/agent_worksdel.jsp file. The ID GET parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. The exploit is publicly available and the CVSS 9.8 score indicates critical impact requiring immediate attention.
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= 9.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.
-
Identify Yonyou KSOA installation and versionLocate the Yonyou KSOA installation directory and check version information in product documentation, About pages, or installation files. Common paths may include /ksoa or similar application directories.Affected if The installed version is Yonyou KSOA 9.0
-
Verify the vulnerable JSP file existsCheck for the presence of /worksheet/agent_worksdel.jsp in the web application's document root or deployed application directory.Affected if The file agent_worksdel.jsp exists in the /worksheet/ directory of the deployed application
-
Confirm the ID parameter is accessibleAttempt to access the endpoint with a GET request to /worksheet/agent_worksdel.jsp and verify the application processes the ID parameter.Affected if The endpoint responds and accepts the ID parameter without requiring authentication or input sanitization
-
Check if application is network exposedDetermine if the Yonyou KSOA web interface is accessible from network locations, including external networks or the internet.Affected if The application is exposed to untrusted networks without proper network segmentation or authentication gates
You are affected if Yonyou KSOA version 9.0 is deployed with the /worksheet/agent_worksdel.jsp endpoint accessible and the application processes the ID parameter without sanitization.
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 all database operations involving the ID parameter. Apply input validation and restrict database privileges to limit the impact of any successful SQL injection.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15424 — 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-15424 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