CVE-2025-6311VulnerabilityPublished 20 Jun 2025

CVE-2025-6311: Campcodes Sales and Inventory System · SQL Injection

Affects Campcodes Sales and Inventory SystemSource 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 41% 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 20 Jun 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
GitHubdragonghost2025/cve`pkg:github/dragonghost2025/cve`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate implementation of input validation and parameterized queries within the /pages/account_add.php file to sanitize 'id' and 'amount' parameters, preventing SQL injection. 2. Deploy Web Application Firewalls (WAFs) configured with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoints. 3. Conduct a comprehensive code review and security audit of the Campcodes Sales and Inventory System to identify and remediate similar injection flaws. 4. Isolate the affected system within the network using segmentation to limit exposure and restrict access to trusted IP addresses where feasible. 5. Monitor logs for unusual database query patterns or repeated failed attempts to exploit the injection vectors. 6. Engage with the vendor for official patches or updates and prioritize their deployment once available. 7. Educate IT and security teams on the specific indicators of compromise related to this vulnerability to enable rapid detection and response. 8. Consider temporary mitigation by disabling or restricting access to the vulnerable functionality if business operations allow.

Description

A vulnerability, which was classified as critical, was found in Campcodes Sales and Inventory System 1.0. This affects an unknown part of the file /pages/account_add.php. The manipulation of the argument id/amount leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using Campcodes Sales and Inventory System 1.0, this vulnerability could lead to unauthorized access to sensitive business data such as customer accounts, sales records, and inventory levels. This could result in financial losses, operational disruptions, and reputational damage. Attackers might alter inventory data, causing stock mismanagement, or extract confidential sales information, impacting competitive advantage. The integrity of financial reporting and compliance with data protection regulations (e.g., GDPR) could be compromised if personal or transactional data is exposed or manipulated. Furthermore, the ability to remotely exploit this vulnerability without authentication increases the risk of widespread attacks, especially in sectors with high reliance on such systems, including retail, wholesale, and manufacturing industries across Europe. The medium severity rating suggests that while the impact is significant, it may not lead to full system compromise or widespread availability disruption, but targeted attacks could still cause substantial business impact.

Summary

CVE-2025-6311 is a SQL Injection vulnerability identified in version 1.0 of the Campcodes Sales and Inventory System, specifically within the /pages/account_add.php file. The vulnerability arises due to improper sanitization or validation of user-supplied input parameters 'id' and 'amount', which are directly incorporated into SQL queries. This flaw allows an unauthenticated remote attacker to inject malicious SQL code, potentially manipulating the backend database. The vulnerability does not require any user interaction or privileges, making exploitation straightforward over the network. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the ease of exploitation (network accessible, no authentication), but limited impact on confidentiality, integrity, and availability (each rated low). Exploitation could lead to unauthorized data access, modification, or deletion within the affected database, potentially disrupting sales and inventory operations. Although no known exploits are currently observed in the wild, the public disclosure of the vulnerability increases the risk of exploitation attempts. The absence of available patches or mitigations from the vendor at this time further elevates the threat. Given the critical nature of sales and inventory systems in business operations, this vulnerability poses a tangible risk to organizations relying on Campcodes version 1.0 for their transactional and inventory management processes.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Jun 2025, 06:01 UTC

Technical details

References

Community reviews

Related threats