dbcve.org
Simple Food Ordering SystemApplication · Fabian

CVE-2025-12301

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-27
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 security vulnerability has been detected in code-projects Simple Food Ordering System 1.0. Impacted is an unknown function of the file /editproduct.php. Such manipulation of the argument photo leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed publicly 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

The Simple Food Ordering System 1.0 contains an unrestricted file upload vulnerability in /editproduct.php via the 'photo' parameter. Attackers can upload malicious files (e.g., PHP webshells, executables) without proper validation, potentially achieving remote code execution on the server.

MitigationImplement strict server-side file validation including MIME type verification, extension allowlist, file content validation, randomize filenames, and store uploads outside the web root. Also enforce proper authentication/authorization on the editproduct.php endpoint.

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
Simple Food 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 installed Simple Food Ordering System version
    Locate version information in the application source code, typically in a README file, version config, or header comments of PHP files. Search for files containing 'version', '1.0', or check the application root directory for version documentation.
    Affected if The installed version is Simple Food Ordering System 1.0 (exact match)
  2. Confirm editproduct.php exists and is accessible
    Check if the file /editproduct.php exists in the web root directory of the application. Verify the file is accessible via HTTP/HTTPS request to the deployed application.
    Affected if The file editproduct.php exists and is web-accessible in the deployed application
  3. Check if photo upload functionality is enabled
    Inspect the editproduct.php source code to determine if the 'photo' parameter accepts file uploads. Look for HTML forms with enctype='multipart/form-data' and input type='file' name='photo'.
    Affected if The 'photo' parameter accepts file uploads without proper restrictions in editproduct.php
  4. Verify upload directory is web-accessible
    Examine the application code to identify the upload directory path used for storing uploaded photos. Check if this directory is located within the web root (publicly accessible).
    Affected if Uploaded files are stored in a directory accessible via web browser without execution restrictions
  5. Check authentication on editproduct.php endpoint
    Review the editproduct.php file for session checks, login verification, or access control logic before allowing file uploads. Look for code that validates user身份 before processing uploads.
    Affected if The endpoint lacks proper authentication or authorization checks before accepting file uploads

The environment is affected if Simple Food Ordering System version 1.0 is deployed with the editproduct.php file accessible and the photo upload feature functional without proper authentication and file validation controls.

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 strict server-side file validation including MIME type verification, extension allowlist, file content validation, randomize filenames, and store uploads outside the web root. Also enforce proper authentication/authorization on the editproduct.php endpoint.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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