dbcve.org
Online Bidding SystemApplication · Fabian

CVE-2025-10802

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 flaw has been found in code-projects Online Bidding System 1.0. Affected is an unknown function of the file /administrator/remove.php. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been published 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 · moderate confidence

SQL injection vulnerability in the Online Bidding System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /administrator/remove.php. The vulnerability is exploitable without authentication and has a publicly available exploit.

MitigationImplement parameterized queries (prepared statements) for all database operations in remove.php, especially those using the ID parameter. Validate and sanitize all user inputs before using them in SQL 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
Online Bidding SystemApplication
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 Bidding System installation
    Locate the web application directory. Check for typical installation paths such as /var/www/html/, /www/, or C:\inetpub\wwwroot\. Look for folders named 'bidding', 'online-bidding', or 'administrator'.
    Affected if The Online Bidding System 1.0 is installed on the server.
  2. Identify installed version
    Check for version information in the application. Look at the main index.php, about.php, or README files for a version number. Check any config or setup files for version indicators.
    Affected if The installed version is 1.0 (exact match).
  3. Verify vulnerable file exists
    Locate the file remove.php within the administrator directory. Typical path: /administrator/remove.php. Check if this file exists in the web root.
    Affected if The file /administrator/remove.php exists in the web application directory.
  4. Inspect remove.php for vulnerable code
    Open remove.php in a text editor or use 'grep' to search for the ID parameter usage. Look for SQL queries that include the ID parameter without prepared statements or sanitization functions like mysqli_prepare, PDO::prepare, or mysql_real_escape_string.
    Affected if The file contains SQL queries using the ID parameter directly without parameterized queries or input sanitization.
  5. Check if application is network-accessible
    Determine if the web server hosting the application is accessible from the network. Test access to the /administrator/ remove.php endpoint using a browser or curl command.
    Affected if The application is accessible over HTTP/HTTPS, allowing external requests to reach the vulnerable script.

You are affected if Online Bidding System version 1.0 is installed, the /administrator/remove.php file exists, and the ID parameter is used in 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations in remove.php, especially those using the ID parameter. Validate and sanitize all user inputs before using them in SQL queries.

Fix this in Online Bidding System 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-10802 — 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-10802 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