CVE-2025-15420
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 vulnerability has been detected in Yonyou KSOA 9.0. This affects an unknown part of the file /worksheet/agent_work_report.jsp. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed publicly and may 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 confidenceCritical SQL injection vulnerability in Yonyou KSOA 9.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /worksheet/agent_work_report.jsp. The attack requires no authentication and can be exploited remotely using the publicly available exploit.
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.
-
Confirm Yonyou KSOA installationLocate the Yonyou KSOA application installation directory or web application root on the server. Check for the presence of the 'ksoa' or 'KSOA' directory in the web server's webapp/application folder.Affected if Yonyou KSOA is installed and accessible on the system
-
Verify installed version is 9.0Check the version information of the installed KSOA instance. This may be found in version files, the application's about page, or configuration files within the KSOA installation directory. Compare your installed version to the affected range (version 9.0).Affected if The installed version is exactly 9.0
-
Check for vulnerable JSP fileInspect the web application's file system for the presence of /worksheet/agent_work_report.jsp in the KSOA web root directory.Affected if The file /worksheet/agent_work_report.jsp exists in the application
-
Confirm ID parameter acceptanceReview the source code of agent_work_report.jsp if accessible, or test sending a request to the endpoint with a test value in the ID parameter (e.g., /worksheet/agent_work_report.jsp?id=test).Affected if The ID parameter is accepted and processed by the JSP file without proper input validation
The environment is affected if Yonyou KSOA version 9.0 is installed and the /worksheet/agent_work_report.jsp file is accessible with the ID parameter accepting user input.
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 immediate input validation and replace dynamic SQL queries with parameterized queries/prepared statements in the affected JSP file. Consider restricting network access to the vulnerable endpoint until a patch is applied.
- 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-15420 — 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-15420 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