CVE-2025-15434
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 detected in Yonyou KSOA 9.0. Affected is an unknown function of the file /kp/PrintZPYG.jsp. The manipulation of the argument zpjhid results in sql injection. It is possible to launch the attack remotely. The exploit is now 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 allows remote attackers to inject arbitrary SQL commands via the 'zpjhid' parameter in the /kp/PrintZPYG.jsp file. The vulnerability is exploitable remotely with a public exploit available.
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 installationCheck for Yonyou KSOA web application by accessing the application's login page or checking for 'KSOA' branding in the application. Query the application server for installed software or check the web root for Yonyou-related directories.Affected if Yonyou KSOA is installed and running
-
Identify installed KSOA versionCheck the application version through the web interface, typically found in the login page footer, about page, or by inspecting the application's system information panel. Alternatively, check version files in the installation directory or contact Yonyou support for version verification.Affected if Version is 9.0 (exact match)
-
Locate vulnerable PrintZPYG.jsp fileAccess the URL path /kp/PrintZPYG.jsp on the server to verify the file exists and is accessible. Check if the application returns a valid response or error message indicating the file is present.Affected if File /kp/PrintZPYG.jsp exists and is reachable via HTTP/HTTPS
-
Test zpjhid parameter for SQL injectionSend a crafted request to /kp/PrintZPYG.jsp with the zpjhid parameter containing SQL injection payloads (e.g., zpjhid=1' OR '1'='1). Observe if the application returns database errors, unexpected data, or behaves differently compared to normal requests.Affected if The zpjhid parameter accepts unsanitized input and reflects SQL syntax in database errors or output
Affected if running Yonyou KSOA version 9.0 AND the /kp/PrintZPYG.jsp endpoint is accessible AND the zpjhid parameter processes SQL 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 immediate compensating controls such as WAF rules or input validation at the application layer; consider migrating to an alternative solution given the vendor's non-responsive posture.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15434 — 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-15434 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