CVE-2025-14245
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 IdeaCMS up to 1.8. This affects the function whereRaw of the file app/common/logic/index/Coupon.php. Such manipulation of the argument params leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
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 confidenceA SQL injection vulnerability exists in IdeaCMS up to version 1.8 in the whereRaw function of app/common/logic/index/Coupon.php. The params argument is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The CVSS score of 9.8 indicates critical severity with no authentication required.
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.8CVSS 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.
-
Locate the Coupon.php fileSearch for Coupon.php in the web root of your IdeaCMS installation, typically found in application/controllers, app/controllers, or a modules directory.Affected if The file exists in your IdeaCMS installation
-
Identify the IdeaCMS versionCheck the version.php, version.json, or composer.json file in your IdeaCMS root directory for the installed version number.Affected if The installed version is 1.8 or lower
-
Examine the whereRaw call in Coupon.phpOpen Coupon.php and search for the whereRaw function call. Inspect whether the 'params' argument is used directly in the query string without parameter binding.Affected if The code shows whereRaw being called with unsanitized params, such as whereRaw("...", $params) where $params is user-controlled and not bound as a prepared statement parameter
-
Verify the application uses the vulnerable endpointCheck if the coupon functionality is enabled and accessible in your application. Look for routes or URL patterns related to coupons that would trigger the vulnerable code path.Affected if The coupon module is active and accessible, allowing requests to reach the vulnerable whereRaw function
Your environment is affected if you are running IdeaCMS version 1.8 or lower, the Coupon.php file exists with the vulnerable whereRaw pattern, and the coupon functionality is enabled and exposed.
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 dataUpgrade IdeaCMS to a version beyond 1.8 that includes the security patch. If no patched version is available, implement input validation and use parameterized queries instead of raw SQL execution in the whereRaw function.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14245 — 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-14245 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