CVE-2025-13582
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 security flaw has been discovered in code-projects Jonnys Liquor 1.0. Affected by this issue is some unknown functionality of the file /detail.php of the component GET Parameter Handler. Performing manipulation of the argument Product results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited.
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 confidenceA SQL injection vulnerability exists in Jonnys Liquor 1.0's /detail.php file via the 'Product' GET parameter. Attackers can manipulate this parameter to inject arbitrary SQL queries, potentially allowing unauthorized database access, data exfiltration, or data modification.
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 Jonnys Liquor installationSearch the web root directory for files containing 'Jonnys Liquor', 'Jonnys', or 'liquor' in application branding. Check for detail.php in the web-accessible directory.Affected if The application 'Jonnys Liquor' version 1.0 is installed on the server.
-
Locate vulnerable detail.php fileSearch the web directory for detail.php. Common paths include the root directory or subdirectories like /detail.php, /product/detail.php, or similar paths containing 'detail.php'.Affected if The file detail.php exists in the web application directory.
-
Inspect Product parameter handlingExamine detail.php and search for usage of $_GET['Product'] or $_REQUEST['Product']. Check if this parameter value is directly concatenated into SQL queries without proper escaping or use of prepared statements.Affected if The code uses the 'Product' GET parameter in SQL queries without parameterized queries or input sanitization.
-
Check for direct SQL string constructionIn detail.php, look for patterns like mysql_query, mysqli_query, or PDO query methods where the 'Product' parameter is embedded directly into the SQL string using string concatenation or interpolation.Affected if SQL queries in detail.php construct query strings by directly inserting the Product parameter value without using prepared statements or binding parameters.
If Jonnys Liquor 1.0 is installed, detail.php exists, and the Product parameter is used directly in SQL queries without prepared statements or input sanitization, the environment is vulnerable to CVE-2025-13582.
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 all dynamic SQL queries in detail.php with parameterized queries/prepared statements. Validate and sanitize all user inputs before using them in database operations.
- Consultation4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13582 — 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-13582 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