dbcve.org
Simple Shopping CartApplication · Fabian

CVE-2025-14246

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in code-projects Simple Shopping Cart 1.0. This vulnerability affects unknown code of the file /Customers/settings.php. Performing manipulation of the argument user_id results in sql injection. Remote exploitation of the attack is possible. The exploit has been made public and could 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 confidence

SQL injection vulnerability in Simple Shopping Cart 1.0 allows remote attackers to inject malicious SQL queries via the user_id parameter in /Customers/settings.php. The vulnerable code directly incorporates user input into SQL queries without proper sanitization or parameterized statements, enabling complete database compromise.

MitigationReplace direct SQL query construction with parameterized queries or prepared statements for the user_id parameter in /Customers/settings.php. Validate and sanitize all user inputs before using them in database queries.

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
Simple Shopping CartApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Simple Shopping Cart installation
    Locate the Simple Shopping Cart application files on the server. Check for the presence of the /Customers/settings.php file mentioned in the CVE. Common locations include web root directories such as /var/www/html/ or c:/xampp/htdocs/.
    Affected if The Simple Shopping Cart application is installed and the file /Customers/settings.php exists.
  2. Confirm installed version is 1.0
    Examine the application source code for a version indicator. Look in the main PHP files (such as index.php, header.php, or a dedicated version/config file) for a version string. Compare the found version against the affected range (= 1.0).
    Affected if The installed version is exactly 1.0.
  3. Locate the vulnerable code in settings.php
    Open the file /Customers/settings.php and search for code that uses the user_id parameter in SQL queries. Look for patterns where $_GET['user_id'] or $_POST['user_id'] is directly concatenated into SQL statements without using prepared statements, parameter binding, or sanitization functions.
    Affected if The file contains SQL queries that directly incorporate the user_id parameter without parameterized queries or input sanitization.
  4. Verify the vulnerable parameter is accessible
    Check if the web server is configured to serve the Simple Shopping Cart application and if the /Customers/settings.php endpoint is accessible via HTTP/HTTPS. Confirm that the user_id parameter can be passed via GET or POST requests to this script.
    Affected if The application is running and the settings.php endpoint accepts user_id input via request parameters.
  5. Confirm database user privileges
    Review the database configuration file (commonly config.php or db.php in the application root) to determine the database user credentials used by the application. The SQL injection allows any SQL command the application database user can execute.
    Affected if The application connects to the database with a user that has privileges beyond read-only access, enabling the injected SQL to potentially modify or exfiltrate data.

You are affected if Simple Shopping Cart version 1.0 is installed, the /Customers/settings.php file exists with direct user_id SQL injection, and the application is accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct SQL query construction with parameterized queries or prepared statements for the user_id parameter in /Customers/settings.php. Validate and sanitize all user inputs before using them in database queries.

Fix this in Simple Shopping Cart Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14246 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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