CVE-2025-6124
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 · uneditedA vulnerability was found in code-projects Restaurant Order System 1.0 and classified as critical. This issue affects some unknown processing of the file /tablelow.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public 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 confidenceSQL injection vulnerability in Restaurant Order System 1.0 allows remote attackers to execute arbitrary SQL commands via the ID parameter in /tablelow.php. The lack of input sanitization enables attackers to manipulate database 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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed applicationLocate and examine the web application's header, footer, or about page for the product name and version information. Check the source code comments or configuration files for 'Restaurant Order System' or 'Carmelogarcia' identifiers.Affected if The application is identified as Carmelogarcia Restaurant Order System version 1.0
-
Verify tablelow.php existsCheck the web server document root for the file /tablelow.php or /php/tablelow.php. Use directory enumeration or access logs to confirm the file is present.Affected if The file tablelow.php exists in the web application directory
-
Confirm the ID parameter is acceptedSubmit an HTTP GET or POST request to tablelow.php with an ID parameter (e.g., ?id=1) and observe if the application processes it without rejecting or sanitizing the input.Affected if The ID parameter is accepted and processed by tablelow.php without input validation or error handling
-
Inspect the source code for SQL injection vulnerabilitiesExamine tablelow.php source code for direct use of $_GET['id'] or $_POST['id'] in SQL queries without prepared statements, parameter binding, or input sanitization functions like mysqli_real_escape_string.Affected if The code contains unsanitized SQL queries using the ID parameter
-
Check if database error messages are exposedSubmit malformed SQL input to the ID parameter and check if detailed database error messages are returned in the HTTP response.Affected if Detailed SQL errors or database messages are visible in the response, indicating lack of error handling
The environment is affected if Carmelogarcia Restaurant Order System version 1.0 is running with the tablelow.php file accessible and processing the ID parameter without input sanitization or parameterized queries.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries (prepared statements) for all database operations in tablelow.php, or disable the vulnerable endpoint until a fix is applied. Consider deploying a WAF as an interim control.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6124 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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