CVE-2025-14091
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 weakness has been identified in TrippWasTaken PHP-Guitar-Shop up to 6ce0868889617c1975982aae6df8e49555d0d555. This vulnerability affects unknown code of the file /product.php of the component Product Details Page. Executing manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The vendor was contacted early about this disclosure but did not respond in any way.
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 PHP-Guitar-Shop product.php allows remote attackers to inject malicious SQL queries via the untrusted ID parameter in the Product Details Page. The vulnerability stems from improper input sanitization when handling the ID argument, potentially enabling unauthorized data access or manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 PHP-Guitar-Shop installationSearch your web server directories for files named 'product.php' or folders containing 'guitar-shop' or similar naming patterns common to this application.Affected if The application files exist on the server and are web-accessible.
-
Identify the product.php fileOpen product.php in a text editor and locate the code handling the 'ID' parameter (commonly via $_GET['ID'] or $_REQUEST['ID']).Affected if The file exists and retrieves an ID parameter from user input.
-
Examine SQL query construction for the ID parameterSearch within product.php for SQL SELECT/INSERT/UPDATE/DELETE statements that directly concatenate or embed the ID parameter into the query string without using prepared statements or parameter binding.Affected if The code contains SQL queries where the ID parameter is inserted directly into the query string (e.g., 'SELECT * FROM products WHERE id=' . $_GET['ID']).
-
Verify input sanitization statusLook for functions like mysqli_real_escape_string, htmlspecialchars, intval type casting, or other validation routines applied to the ID parameter before its use in SQL queries.Affected if No sanitization functions are found, or sanitization is applied inconsistently/not at all before SQL execution.
-
Confirm database interactionCheck if the product.php page connects to a database and executes the query identified in step 3. Verify the query is actually used in a mysqli_query, $pdo->query, or similar database execution function.Affected if The unsanitized ID parameter is passed directly to a database execution function.
You are affected if PHP-Guitar-Shop is installed and product.php contains direct SQL query construction using the user-supplied ID parameter without prepared statements or proper 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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the ID parameter, implement strict input validation, and consider deploying a WAF as a temporary layer of defense.
- Consultation3.0 h
- Implementation8.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14091 — 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-14091 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