dbcve.org
Online Frozen Foods Ordering SystemApplication · Itsourcecode

CVE-2025-15073

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-24
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 determined in itsourcecode Online Frozen Foods Ordering System 1.0. This affects an unknown part of the file /contact_us.php. This manipulation of the argument Name causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.

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 critical SQL injection vulnerability exists in the itsourcecode Online Frozen Foods Ordering System 1.0 in the /contact_us.php file. The 'Name' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL statements. The public disclosure of this exploit increases the likelihood of targeted attacks.

MitigationImmediately implement parameterized queries or prepared statements for all user inputs in contact_us.php, particularly the Name parameter. Apply input validation and sanitize all user-supplied data. Consider deploying a WAF as a temporary compensating control until the code fix is implemented.

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 Frozen Foods 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. Locate the vulnerable contact_us.php file
    Search the web root directory for the file /contact_us.php (or contact_us.php) - common paths may include /var/www/html/, /www/, or the application's web directory.
    Affected if The file contact_us.php exists in the web application directory.
  2. Identify the application version
    Check for version indicators such as a README file, version in footer pages, or metadata files. Inspect the source code for version comments or check any admin panel for version info.
    Affected if The application version is exactly 1.0 (or if version cannot be determined but the vulnerable file exists).
  3. Examine the contact_us.php source code for SQL injection vulnerability
    Open contact_us.php and search for SQL query patterns involving the 'Name' or 'name' parameter. Look for dynamic SQL construction without parameterized queries or input sanitization (e.g., direct concatenation of $_POST['name'] into SQL strings).
    Affected if The code contains dynamic SQL queries using the Name parameter without prepared statements, parameterized queries, or proper escaping functions.
  4. Verify the contact form endpoint accepts Name parameter
    Review the HTML form in contact_us.php to confirm it accepts a 'Name' input field and submits it via POST to the same script or a backend handler.
    Affected if The contact form has a Name input field that is submitted to the vulnerable PHP script.
  5. Check if the application database uses dynamic SQL in the contact form handler
    In contact_us.php, locate the code that processes the form submission. Look for INSERT or UPDATE statements that incorporate the Name parameter directly into the SQL query string.
    Affected if The form handler builds SQL queries dynamically using the Name parameter without using mysqli_prepare, PDO prepare, or equivalent.

The environment is affected if the Itsourcecode Online Frozen Foods Ordering System version 1.0 is running and the contact_us.php file contains dynamic SQL queries that incorporate the Name 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

Immediately implement parameterized queries or prepared statements for all user inputs in contact_us.php, particularly the Name parameter. Apply input validation and sanitize all user-supplied data. Consider deploying a WAF as a temporary compensating control until the code fix is implemented.

Fix this in Online Frozen Foods Ordering System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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