dbcve.org
Online Shoe StoreApplication · Code Projects

CVE-2025-6317

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 classified as critical has been found in code-projects Online Shoe Store 1.0. This affects an unknown part of the file /admin/confirm.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack 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 /admin/confirm.php via the ID parameter in the Online Shoe Store 1.0 application. The lack of parameterized queries allows remote attackers to inject malicious SQL statements. The critical CVSS score indicates potential for complete system compromise.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in confirm.php, implement strict input validation on the ID parameter, and apply least-privilege 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 1.0 is installed
    Search for the application files, particularly look for a folder structure containing 'Online Shoe Store' or 'shoe' in the web root directory. Check for the presence of confirm.php in an /admin/ directory.
    Affected if The application files with version 1.0 are present on the server
  2. Locate the vulnerable confirm.php file
    Navigate to the /admin/ directory and locate confirm.php. The file path typically follows: /admin/confirm.php or similar within the web application root.
    Affected if The file /admin/confirm.php exists in the web application
  3. Check the application version
    Look for a version file, readme, or check the source code for version indicators. Common locations include a /includes/ folder, footer in main pages, or a dedicated version.txt file.
    Affected if The installed version is exactly 1.0
  4. Inspect confirm.php for SQL injection vulnerability
    Open confirm.php and examine the code around the ID parameter. Look for SQL queries that directly incorporate the ID parameter (e.g., 'SELECT * FROM table WHERE id=' . $_GET['id']) without using prepared statements, parameterized queries, or binding functions.
    Affected if The ID parameter is used in a SQL query without parameterized queries or input sanitization (dynamic string concatenation is observed)
  5. Verify admin endpoint is accessible
    Attempt to access the /admin/confirm.php endpoint via HTTP request to confirm it is reachable. Check if the application routing or server configuration allows access to this file.
    Affected if The /admin/confirm.php endpoint is accessible from the network

You are affected if the Online Shoe Store version 1.0 is installed, the /admin/confirm.php file exists, and the ID parameter in that file is handled via dynamic SQL concatenation rather than parameterized queries.

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 prepared statements/parameterized queries in confirm.php, implement strict input validation on the ID parameter, and apply least-privilege database accounts.

Fix this in Online Shoe Store Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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