CVE-2025-3956
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 201206030 novel-cloud 1.4.0 and classified as critical. This vulnerability affects the function RestResp of the file novel-cloud-master/novel-book/novel-book-service/src/main/resources/mapper/BookInfoMapper.xml. The manipulation leads to sql injection. The attack can be initiated 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 · moderate confidenceA SQL injection vulnerability exists in the BookInfoMapper.xml file of novel-cloud version 1.4.0 within the RestResp function. The vulnerability allows remote attackers to execute arbitrary SQL commands by manipulating input parameters, likely due to unsafe use of ${} parameter binding instead of #{} in MyBatis mapper configuration.
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= 1.4.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 novel-cloud versionLocate the novel-cloud application and determine its installed version number, typically found in build configuration files (pom.xml, build.gradle), version manifests, or the application's about/info endpointAffected if The installed version is exactly 1.4.0
-
Locate BookInfoMapper.xmlFind the BookInfoMapper.xml MyBatis mapper file within the novel-cloud application codebase, typically under src/main/resources/mapper/ or similar resources directoryAffected if The file exists in the application
-
Inspect RestResp function queryOpen BookInfoMapper.xml and locate the SQL query definition associated with the RestResp function or methodAffected if A query named RestResp or related to RestResp exists in the mapper file
-
Check for unsafe parameter bindingExamine the RestResp SQL query for the presence of ${} parameter placeholders (for example, ${parameterName}) which allow direct string substitution, as opposed to #{} placeholders which use prepared statement parameter bindingAffected if The RestResp query contains ${} parameter expressions that could allow SQL injection
The environment is affected if novel-cloud version 1.4.0 is installed AND the BookInfoMapper.xml file contains the RestResp function using unsafe ${} parameter binding in the SQL query.
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 dataReplace unsafe MyBatis parameter expressions (${}) with parameterized queries (#{}) in BookInfoMapper.xml and audit other mapper files for similar SQL injection patterns. Input validation should also be implemented as a defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3956 — 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-3956 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