CVE-2025-13582VulnerabilityPublished 24 Nov 2025

CVE-2025-13582: code-projects Jonnys Liquor · SQL Injection

Affects code-projects Jonnys LiquorSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Jonnys Liquor	Affected =1.0	Fixed in–

AI-suggested

1. Immediately audit all instances of code-projects Jonnys Liquor 1.0 for the presence of the vulnerable /detail.php component. 2. Implement strict input validation and sanitization on the 'Product' GET parameter to reject or neutralize malicious input. 3. Refactor database queries to use parameterized statements or prepared queries to prevent SQL injection. 4. Monitor network traffic and application logs for unusual or suspicious requests targeting the 'Product' parameter. 5. Restrict access to the affected application components via web application firewalls (WAFs) with custom rules blocking SQL injection patterns. 6. Engage with the vendor or community to obtain patches or updates addressing this vulnerability and apply them as soon as available. 7. Conduct regular security assessments and penetration testing focusing on injection flaws. 8. Educate developers and administrators on secure coding and configuration practices to prevent similar vulnerabilities.

Description

A 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.

Impact

For European organizations, this vulnerability poses a risk of unauthorized access to sensitive customer and business data stored in the Jonnys Liquor application database. Exploitation could lead to data leakage, loss of data integrity, or disruption of service availability, impacting business operations and customer trust. Retailers and e-commerce platforms using this software may face regulatory repercussions under GDPR if personal data is compromised. The medium severity score reflects a moderate but tangible threat, especially given the remote and unauthenticated nature of the exploit. The public release of an exploit increases the urgency for European entities to address this vulnerability promptly. Additionally, the potential for data manipulation could affect inventory management and sales reporting, leading to financial losses and reputational damage.

Summary

CVE-2025-13582 identifies a SQL injection vulnerability in the code-projects Jonnys Liquor 1.0 application, specifically within the /detail.php component that handles GET parameters. The vulnerability arises from improper sanitization of the 'Product' parameter, allowing an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. This can lead to unauthorized data access, modification, or deletion within the backend database. The vulnerability is exploitable over the network with low attack complexity and no privileges required, as indicated by the CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N). The impact on confidentiality, integrity, and availability is limited but significant enough to warrant concern, as attackers could extract sensitive information or corrupt data. Although no active exploits have been observed in the wild, the public availability of an exploit increases the likelihood of attacks. The lack of patches at the time of disclosure necessitates immediate mitigation through secure coding practices such as input validation and the use of parameterized queries. Organizations relying on this software should prioritize vulnerability assessment and remediation to prevent potential breaches.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Dec 2025, 05:19 UTC

Technical details

References

Community reviews

Related threats