dbcve.org
Simple E Commerce BookstoreApplication · Janobe

CVE-2025-11430

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-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 SourceCodester Simple E-Commerce Bookstore 1.0. The affected element is an unknown function of the file /cart.php. The manipulation of the argument remove results in sql injection. The attack can be executed remotely. 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 SourceCodester Simple E-Commerce Bookstore 1.0 cart.php file. The 'remove' parameter is not properly sanitized, allowing attackers to inject malicious SQL queries remotely.

MitigationReplace dynamic SQL queries in cart.php with parameterized queries or prepared statements to neutralize the injection vector.

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 E Commerce BookstoreApplication
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. Locate the cart.php file
    Search the web server document root for cart.php (e.g., find /var/www -name cart.php or search for cart.php in the application directory)
    Affected if The file /cart.php exists in the application web root
  2. Confirm the application version
    Check the application version by reviewing any version files, README, or footer/copyright text in the application - look for '1.0' or 'Simple E-Commerce Bookstore'
    Affected if The installed version is Simple E-Commerce Bookstore version 1.0
  3. Verify the remove parameter is handled by cart.php
    Review the source code of cart.php and locate the code that handles the 'remove' parameter (search for $_GET['remove'] or $_POST['remove'] or 'remove')
    Affected if cart.php processes a 'remove' parameter from user input without proper sanitization or parameterized queries
  4. Check if user input reaches the database unsanitized
    Examine the cart.php code around the 'remove' parameter handling - look for SQL queries that directly concatenate the remove parameter value without using prepared statements, parameterized queries, or escaping functions
    Affected if The 'remove' parameter value is directly inserted into an SQL query without input sanitization or use of prepared statements

You are affected if the application is Simple E-Commerce Bookstore version 1.0 and the cart.php file processes a 'remove' parameter from user input directly into SQL queries without sanitization or prepared statements.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries in cart.php with parameterized queries or prepared statements to neutralize the injection vector.

Recommended fix Moderate confidence
  1. This vulnerability is in a PHP script from SourceCodester (sourcecodester.com) which does not provide formal security patches or version updates.
  2. The application Simple E-Commerce Bookstore 1.0 is a standalone PHP script, not a maintained software product with security support.
  3. To remediate: Implement parameterized queries (prepared statements) in /cart.php for the 'remove' parameter to prevent SQL injection.
  4. Locate the SQL query in cart.php that uses the 'remove' parameter and replace dynamic SQL concatenation with PDO prepared statements.
  5. Example fix: Replace $sql = "DELETE FROM cart WHERE id = " . $_GET['remove']; with a parameterized query like $stmt = $pdo->prepare('DELETE FROM cart WHERE id = :remove'); $stmt->execute(['remove' => $_GET['remove']]);
  6. After implementing the fix, test the cart functionality to ensure the remove feature still works correctly.
  7. Consider migrating to a maintained e-commerce platform that provides regular security updates.
Caveat No formal upgrade path exists for this application; manual code remediation is required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Simple E Commerce Bookstore Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11430 — 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-11430 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