CVE-2025-15436
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 Yonyou KSOA 9.0. Affected by this issue is some unknown functionality of the file /worksheet/work_edit.jsp. Such manipulation of the argument Report leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public 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 confidenceSQL injection vulnerability in Yonyou KSOA 9.0's /worksheet/work_edit.jsp file allows remote attackers to inject malicious SQL queries through the Report parameter, potentially leading to unauthorized database access or manipulation.
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 installation existsLocate Yonyou KSOA in your environment by identifying the web application's deployment directory or by checking for the characteristic application files and folder structure typically associated with KSOA installations.Affected if Yonyou KSOA is not present in the environment, then this CVE does not apply.
-
Verify the installed KSOA versionDetermine the exact version of Yonyou KSOA by checking the application's version information, typically found in the software's about page, installation metadata, or version file within the deployment directory.Affected if The installed version is not 9.0, then this CVE does not apply.
-
Check for presence of vulnerable work_edit.jspLocate the /worksheet/work_edit.jsp file within the web application's deployment directory. This file should exist in the worksheet subdirectory of the web root.Affected if The work_edit.jsp file does not exist in the expected location, then this specific CVE may not be present.
-
Verify network accessibility of the vulnerable endpointConfirm whether the web application and specifically the /worksheet/work_edit.jsp endpoint is accessible from the network by attempting to access the URL or reviewing network exposure configurations.Affected if The application is not network-accessible (only localhost or strictly internal), the exploit vector is significantly reduced.
-
Inspect the Report parameter handling in work_edit.jspExamine the source code of work_edit.jsp to verify that the Report parameter is directly incorporated into SQL queries without proper parameterized query implementation or input sanitization.Affected if The Report parameter uses prepared statements or proper input sanitization, the SQL injection vulnerability is mitigated.
The environment is affected if Yonyou KSOA version 9.0 is installed, the /worksheet/work_edit.jsp file exists, and the Report parameter is handled without parameterized queries in the application's code.
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 Report parameter in work_edit.jsp to prevent SQL injection. Since the vendor did not respond, consider network segmentation to limit exposure and monitor for exploitation attempts.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15436 — 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-15436 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