dbcve.org
Online Ordering SystemApplication · Fabian

CVE-2025-8248

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-28
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 was found in code-projects Online Ordering System 1.0. This vulnerability affects unknown code of the file /signup.php. The manipulation of the argument firstname leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

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 Online Ordering System 1.0 signup.php file allows remote attackers to inject malicious SQL queries via the firstname parameter. The vulnerability has a CVSS score of 9.8 (Critical) indicating trivial exploitability and severe impact. Other input parameters in the same file may also be vulnerable.

MitigationImplement prepared statements/parameterized queries for all user inputs in signup.php, expand the audit to identify and remediate SQL injection in other affected parameters, and apply input validation as defense-in-depth.

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 Ordering 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. Identify if Fabian Online Ordering System is installed
    Search the web root directory for files containing 'Online Ordering System' branding, check for the presence of a vendor directory or README file mentioning 'Fabian', or look for the typical installation path structure of this application.
    Affected if The system has Fabian Online Ordering System present on the server.
  2. Verify the installed version
    Check the application version by looking for a version file (version.txt, VERSION, or similar), a README file that lists the version, or the header/comment blocks in core PHP files.
    Affected if The installed version is exactly 1.0.
  3. Locate and verify signup.php accessibility
    Find signup.php in the web-accessible directory (typically in the root or a 'users' folder). Confirm the file is accessible via HTTP/HTTPS by accessing the signup page URL.
    Affected if signup.php exists and is web-accessible.
  4. Inspect signup.php for unsafe SQL construction
    Open signup.php and search for SQL query patterns that directly concatenate user input into query strings (such as $db->query or mysql_query with the firstname variable inserted directly without escaping or parameter binding).
    Affected if The code shows direct string concatenation of the firstname parameter into SQL queries without using prepared statements or parameter binding.
  5. Check if prepared statements are implemented
    Search the signup.php file for function calls like 'prepare', 'bind_param', 'execute', or PDO::prepare with bound parameters. If these are absent and raw variable insertion into SQL is found, the vulnerability exists.
    Affected if Prepared statements are not used for the firstname parameter (or other parameters) in signup.php.
  6. Review database query logs for malicious patterns
    Examine database slow query logs or general logs for entries containing SQL injection payloads in the firstname field, such as unexpected SQL keywords (UNION, SELECT, OR 1=1) appearing in what should be name data.
    Affected if SQL injection payloads are present in logged queries for the firstname field.

A user is affected if Fabian Online Ordering System version 1.0 is installed, signup.php is accessible, and the code does not use prepared statements for the firstname parameter, allowing arbitrary SQL injection.

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 user inputs in signup.php, expand the audit to identify and remediate SQL injection in other affected parameters, and apply input validation as defense-in-depth.

Fix this in Online Ordering System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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