dbcve.org
Food Ordering Review SystemApplication · Carmelo

CVE-2025-7814

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-18
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 Food Ordering Review System 1.0. This vulnerability affects unknown code of the file /pages/signup_function.php. The manipulation of the argument fname 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 fname parameter of /pages/signup_function.php in Food Ordering Review System 1.0 allows remote attackers to inject arbitrary SQL queries. The vulnerability is exploitable without authentication and other signup-related parameters may also be affected.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries for fname and all other user inputs in signup_function.php; implement proper input validation and output encoding.

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
Food Ordering Review 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 Food Ordering Review System is installed
    Locate the web application directory on your server. Check for application files typical of the Carmelo Food Ordering Review System, such as login pages, ordering interfaces, or review modules.
    Affected if The application directory contains the Food Ordering Review System files.
  2. Verify the installed version is 1.0
    Check your application files for version indicators such as version.php, a README file, or any configuration file that displays the software version. Compare against the affected version 1.0.
    Affected if The installed version is exactly 1.0.
  3. Confirm the vulnerable signup_function.php file exists
    Navigate to the /pages/ directory within your web application root and verify that signup_function.php is present. This file handles the signup functionality where the vulnerability exists.
    Affected if The file /pages/signup_function.php exists on the server.
  4. Determine if the signup functionality is publicly accessible
    Access your web application and navigate to the registration or signup page. Verify whether the fname parameter can be submitted via HTTP POST or GET requests to the signup_function.php endpoint.
    Affected if The signup form is accessible and accepts user input including the fname parameter.
  5. Check database user privileges
    Review the database configuration file used by the application to identify the database user credentials. Assess whether this database user has privileges beyond standard SELECT/INSERT/UPDATE/DELETE, such as file permissions, INTO OUTFILE capabilities, or administrative roles.
    Affected if The database user has elevated privileges that could allow OS-level command execution or file operations.

Your environment is affected if the Food Ordering Review System version 1.0 is installed with the /pages/signup_function.php file present and the signup functionality accessible to users.

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 for fname and all other user inputs in signup_function.php; implement proper input validation and output encoding.

Fix this in Food Ordering Review System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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