CVE-2025-14652
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 itsourcecode Online Cake Ordering System 1.0. This issue affects some unknown processing of the file /admindetail.php?action=edit. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been made public and could 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 · moderate confidenceSQL injection vulnerability in itsourcecode Online Cake Ordering System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /admindetail.php?action=edit. The lack of proper input sanitization or parameterized queries 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.
-
Confirm the Online Cake Ordering System is installedSearch your web server document root for files matching 'cake' or 'ordering' in the filename, or look for directories containing 'admindetail.php'. Common paths may include /var/www/html/, /www/, or C:\inetpub\wwwroot\.Affected if The Online Cake Ordering System files are present on the server
-
Verify the installed version is 1.0Look for a version file, README, or any file containing version information within the application directory. Check the source code comments or footer for version strings like '1.0'.Affected if The version is confirmed as 1.0 or if no version information is found but the application matches the product
-
Locate the vulnerable admindetail.php fileFind the file named 'admindetail.php' in the application directory structure. Verify it exists at a path like /admindetail.php or within an admin subdirectory.Affected if The file admindetail.php exists in the application
-
Inspect the ID parameter handling in admindetail.phpOpen admindetail.php in a text editor and search for code that handles the 'ID' or 'id' parameter from the query string (e.g., $_GET['ID']). Check if this parameter is directly concatenated into SQL queries without using prepared statements or escaping functions.Affected if The code directly uses the ID parameter in SQL queries without sanitization or prepared statements
-
Verify the 'edit' action route is accessibleCheck if the URL /admindetail.php?action=edit is accessible through your web server. Confirm the application routes requests to this endpoint and that it processes the ID parameter.Affected if The endpoint responds and processes the ID parameter without validation
You are affected if the Online Cake Ordering System version 1.0 is installed, the admindetail.php file exists, and the ID parameter in the edit action is used in SQL queries without prepared statements or input sanitization.
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 prepared statements/parameterized queries for all database operations, especially on the ID parameter in admindetail.php. Apply input validation and output encoding. Consider deploying a WAF as an additional layer of defense.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14652 — 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-14652 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