CVE-2025-15167
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 determined in itsourcecode Online Cake Ordering System 1.0. This impacts an unknown function of the file /detailtransac.php. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. 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 · moderate confidenceA critical SQL injection vulnerability exists in itsourcecode Online Cake Ordering System 1.0. The ID parameter in /detailtransac.php is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL code. This can lead to unauthorized database access, data exfiltration, or potential system compromise.
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.
-
Locate the vulnerable PHP fileSearch for the file detailtransac.php in your web server's document root. Common paths may include /var/www/html/, /www/, or the application root directory. Use: find / -name 'detailtransac.php' 2>/dev/nullAffected if The file detailtransac.php exists in your web application directory
-
Verify the product versionCheck the application version by inspecting README files, version.php, or the footer of web pages. The affected version is 1.0 of Admerc Online Cake Ordering SystemAffected if The installed version is Admerc Online Cake Ordering System version 1.0
-
Confirm the ID parameter is exposedAccess the detailtransac.php page via HTTP request and verify the ID parameter is accepted, e.g., GET /detailtransac.php?id=1Affected if The page accepts an ID parameter without authentication or proper validation
-
Inspect the source code for SQL injection vulnerabilityOpen detailtransac.php and examine how the ID parameter is handled. Look for unsanitized variable usage in SQL queries, e.g., SELECT * FROM table WHERE id='$id' without prepared statements or escapingAffected if The ID parameter is directly concatenated into SQL queries without parameterized queries, escaping, or input validation
Your environment is affected if you run Admerc Online Cake Ordering System version 1.0 and the file detailtransac.php contains direct SQL query construction using the ID parameter without prepared statements.
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 dataReplace dynamic SQL queries with parameterized statements (prepared statements) and implement proper input validation on all user-supplied parameters. If a patched version is available, upgrade immediately.
- 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-15167 — 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-15167 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