dbcve.org
Online Shoe StoreApplication · Code Projects

CVE-2025-6354

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-20
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, which was classified as critical, has been found in code-projects Online Shoe Store 1.0. Affected by this issue is some unknown functionality of the file /function/customer_signup.php. The manipulation of the argument email 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 confidence

SQL injection vulnerability in the email parameter of /function/customer_signup.php in Online Shoe Store 1.0 allows remote attackers to execute arbitrary SQL commands by injecting malicious payloads through the unvalidated email field.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in customer_signup.php, implement strict input validation on all user-supplied data, and apply principle of least privilege to database accounts.

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
Online Shoe StoreApplication
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. Confirm Online Shoe Store installation
    Locate the web application root directory and identify if the 'Online Shoe Store' application is present. Look for characteristic files such as index.php, header.php, or the /function/ directory.
    Affected if The application is not the Code Projects Online Shoe Store or cannot be found.
  2. Verify the product version
    Check for version information in the application. Look in README files, version.php, or footer/config files for a version number. Also check the source code comments or meta tags that may display the version.
    Affected if The installed version is NOT 1.0 (the only affected version listed).
  3. Locate the vulnerable file
    Navigate to the /function/ directory within the web application root and verify that customer_signup.php exists.
    Affected if The file /function/customer_signup.php does not exist.
  4. Inspect the email parameter handling
    Open customer_signup.php and examine the code that handles the 'email' parameter from POST or GET requests. Look for SQL query construction that uses this parameter without proper escaping or prepared statements.
    Affected if The email parameter is used directly in SQL queries without parameterized queries, prepared statements, or input validation (e.g., no mysqli_prepare, PDO prepare, or escaping functions detected).
  5. Check for SQL injection susceptibility
    Review the SQL query context around the email field. Look for patterns like: $sql = "SELECT * FROM users WHERE email = '$email'" - direct string concatenation of the email variable into the query.
    Affected if The code shows direct string concatenation of the email variable into SQL queries (e.g., "SELECT ... WHERE email = '$email'") without using mysqli_stmt_bind_param or equivalent.

The environment is affected if the Code Projects Online Shoe Store version 1.0 is installed AND the file /function/customer_signup.php exists AND the email parameter is handled with direct string concatenation in SQL queries rather than prepared statements or input validation.

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 dynamic SQL queries with parameterized queries/prepared statements in customer_signup.php, implement strict input validation on all user-supplied data, and apply principle of least privilege to database accounts.

Fix this in Online Shoe Store Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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