CVE-2025-13424VulnerabilityPublished 20 Nov 2025Updated 24 Feb 2026

CVE-2025-13424: Campcodes Supplier Management System · SQL Injection

Affects Campcodes Supplier Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 20 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-26.

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
Campcodes Supplier Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate mitigation should focus on restricting administrative access to the Campcodes Supplier Management System to trusted personnel only, employing strong authentication mechanisms such as multi-factor authentication (MFA). 2. Implement rigorous input validation and parameterized queries or prepared statements in the /admin/add_product.php script to sanitize the txtProductName parameter and prevent SQL injection. 3. Monitor and audit administrative activities and database queries for unusual or suspicious behavior indicative of exploitation attempts. 4. If possible, isolate the supplier management system within a segmented network zone to limit exposure. 5. Engage with the vendor (Campcodes) for official patches or updates addressing this vulnerability and apply them promptly once available. 6. Conduct regular security assessments and penetration testing focused on web application vulnerabilities to identify and remediate similar issues proactively. 7. Educate administrators about the risks of SQL injection and the importance of secure coding practices and access controls. 8. Employ Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the affected parameter.

Description

A vulnerability has been found in Campcodes Supplier Management System 1.0. This affects an unknown function of the file /admin/add_product.php. The manipulation of the argument txtProductName leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.

Impact

The primary impact of this vulnerability is the potential unauthorized access and manipulation of supplier data stored within the Campcodes Supplier Management System database. Attackers with administrative access could leverage the SQL injection to extract sensitive information, alter product or supplier records, or disrupt system availability. This could lead to compromised supply chain data integrity, financial losses, and reputational damage for affected organizations. Since the vulnerability requires administrative privileges, the risk is somewhat mitigated by internal access controls; however, if an attacker gains such access through other means (e.g., credential theft), this vulnerability could be exploited to escalate damage. Organizations relying on this system for critical supplier management functions may face operational disruptions and increased risk of fraud or data breaches. The public disclosure of the exploit increases the likelihood of opportunistic attacks, especially in environments where patching or mitigation is delayed.

Summary

CVE-2025-13424 is an SQL injection vulnerability identified in Campcodes Supplier Management System version 1.0, specifically within the /admin/add_product.php script. The vulnerability stems from improper handling and sanitization of the txtProductName parameter, which is susceptible to malicious SQL payloads. This flaw allows an attacker with administrative privileges to remotely inject SQL commands into the backend database query, potentially manipulating or extracting sensitive data. The vulnerability does not require user interaction but does require the attacker to have high-level privileges (administrator access) on the system, which somewhat limits exploitation scope. The CVSS 4.0 score of 5.1 reflects a medium severity, considering the network attack vector, low complexity, no authentication bypass, and limited impact on confidentiality, integrity, and availability. No patches have been officially released yet, and while the exploit details are publicly available, there are no confirmed reports of active exploitation in the wild. The vulnerability poses risks such as unauthorized data access, data modification, or disruption of supplier management operations if exploited. Given the critical role of supplier management systems in business operations, exploitation could have downstream effects on supply chain integrity and operational continuity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:07 UTC

Technical details

References

Community reviews

Related threats