CVE-2025-14185
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 identified in Yonyou U8 Cloud 5.0/5.0sp/5.1/5.1sp. The affected element is an unknown function of the file nc/pubitf/erm/mobile/appservice/AppServletService.class. Such manipulation of the argument usercode leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might 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 · moderate confidenceSQL injection vulnerability in Yonyou U8 Cloud's AppServletService.class where the usercode parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through the nc/pubitf/erm/mobile/appservice endpoint.
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.
-
Identify if Yonyou U8 Cloud is installedCheck for Yonyou U8 Cloud installation directories, services, or application pools. Common paths may include installation directories for U8 Cloud or check running services/processes for Yonyou components.Affected if Yonyou U8 Cloud software is present in the environment
-
Verify the vulnerable endpoint is accessibleTest connectivity to the nc/pubitf/erm/mobile/appservice endpoint by sending a request to the application's web server on typical ports (80, 443, 8080). Check if the endpoint responds.Affected if The endpoint responds and accepts requests, indicating the module is exposed
-
Confirm the mobile appservice module is enabledCheck application configuration files or web.xml for the erm/mobile/appservice servlet mapping. Look for AppServletService class registration in the application's deployment descriptor.Affected if The AppServletService servlet is registered and enabled in the application configuration
-
Check the usercode parameter handlingReview the AppServletService.class file or decompile it to examine how the usercode parameter is processed. Look for direct string concatenation in SQL queries without parameterized queries or input sanitization.Affected if The usercode parameter is used directly in SQL queries without prepared statements or proper escaping
-
Review application logs for exploitation attemptsExamine web server logs, application logs, and database audit logs for suspicious SQL patterns in usercode parameter values, such as UNION SELECT, OR 1=1, or other SQL injection payloads targeting the appservice endpoint.Affected if Log entries show malicious SQL injection patterns in usercode parameter requests
The environment is affected if Yonyou U8 Cloud is installed with the erm/mobile/appservice endpoint accessible and the AppServletService handling usercode without parameterized queries.
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 usercode parameter; apply input validation and sanitization; consider deploying a WAF as compensating control until the code fix is implemented.
- Consultation4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14185 — 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-14185 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