dbcve.org
E Commerce WebsiteApplication · Fabian

CVE-2025-10793

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-22
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 detected in code-projects E-Commerce Website 1.0. Affected by this vulnerability is an unknown functionality of the file /pages/admin_account_delete.php. Performing manipulation of the argument user_id results in sql injection. It is possible to initiate the attack remotely. The exploit is now 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

A SQL injection vulnerability exists in the admin_account_delete.php file of code-projects E-Commerce Website 1.0. The user_id parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. This can lead to unauthorized database access, data exfiltration, or administrative account compromise.

MitigationImplement prepared statements/parameterized queries for all database operations involving user input, particularly the user_id parameter in admin_account_delete.php. Additionally, apply input validation and least-privilege database accounts to limit the impact of any SQL injection.

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
E Commerce WebsiteApplication
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 the installed application version
    Check the application documentation, headers, or source code files to confirm the installed version is Fabian E Commerce Website version 1.0
    Affected if The application is Fabian E Commerce Website version 1.0
  2. Locate the vulnerable PHP file
    Search for the file admin_account_delete.php in the web application directory structure, typically under an admin or administration folder
    Affected if The file admin_account_delete.php exists in the application
  3. Verify admin interface accessibility
    Check if the admin panel or admin_account_delete.php is accessible via HTTP/HTTPS requests without requiring proper authentication or with weak access controls
    Affected if The admin functionality is exposed without adequate authentication controls
  4. Examine user_id parameter handling
    Review the code in admin_account_delete.php to determine if the user_id parameter is used directly in SQL queries without prepared statements, parameter binding, or input sanitization
    Affected if The user_id parameter is concatenated directly into SQL queries without sanitization or prepared statements
  5. Check database query implementation
    Inspect all database query code in admin_account_delete.php for use of mysqli_prepare, PDO prepare, or similar parameterized query methods versus raw query construction using user input
    Affected if SQL queries are constructed using string concatenation with the user_id parameter instead of parameterized queries

You are affected if you are running Fabian E Commerce Website version 1.0 and the admin_account_delete.php file handles the user_id parameter without prepared statements or input sanitization.

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

Implement prepared statements/parameterized queries for all database operations involving user input, particularly the user_id parameter in admin_account_delete.php. Additionally, apply input validation and least-privilege database accounts to limit the impact of any SQL injection.

Fix this in E Commerce Website Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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