CVE-2025-7120VulnerabilityPublished 7 Jul 2025Updated 15 Jul 2025

CVE-2025-7120: Campcodes Complaint Management System · SQL Injection

Affects Campcodes Complaint Management 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.5% chance of exploitation in 30 days – higher than 45% 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 7 Jul 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
Campcodes Complaint Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate implementation of web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'email' parameter in /users/check_availability.php. 2. Conduct a thorough code review and apply input validation and parameterized queries or prepared statements to sanitize the 'email' input, eliminating direct SQL concatenation. 3. Restrict database user permissions to the minimum necessary to limit the impact of any injection. 4. Monitor logs for unusual query patterns or repeated access to the vulnerable endpoint. 5. Isolate the complaint management system from critical internal networks to contain potential breaches. 6. Engage with the vendor for official patches or updates and plan for an immediate upgrade once available. 7. Perform penetration testing focused on injection vectors to verify the effectiveness of mitigations. 8. Educate IT and security teams about the vulnerability and ensure incident response plans include scenarios involving SQL injection attacks.

Description

A vulnerability was found in Campcodes Complaint Management System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /users/check_availability.php. The manipulation of the argument email leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using Campcodes Complaint Management System 1.0, this vulnerability poses a significant risk to the confidentiality and integrity of complaint data, which may include personal data protected under GDPR. Successful exploitation could result in unauthorized data disclosure, data tampering, or denial of service, impacting customer trust and potentially leading to regulatory penalties. The remote, unauthenticated nature of the exploit increases the attack surface, especially for externally accessible complaint management portals. This could disrupt customer service operations and damage organizational reputation. Additionally, compromised systems could be leveraged as pivot points for further attacks within the network. Given the criticality of complaint handling in sectors like public services, healthcare, and finance, the impact could be severe if exploited.

Summary

CVE-2025-7120 is a critical SQL Injection vulnerability identified in version 1.0 of the Campcodes Complaint Management System. The flaw exists in the /users/check_availability.php script, specifically in the handling of the 'email' parameter. An attacker can remotely manipulate this parameter without authentication or user interaction to inject malicious SQL code. This injection can lead to unauthorized access or modification of the backend database, potentially exposing sensitive complaint data or allowing further compromise of the system. The vulnerability is exploitable over the network (AV:N), requires no privileges (PR:N), no user interaction (UI:N), and has low complexity (AC:L). The impact on confidentiality, integrity, and availability is limited but present (VC:L, VI:L, VA:L). Although no known exploits are currently in the wild, the public disclosure increases the risk of exploitation. The CVSS 4.0 base score is 6.9, categorized as medium severity. The absence of patches or mitigations from the vendor at this time increases the urgency for organizations to implement protective measures. Given the nature of complaint management systems, which often handle personal and sensitive information, exploitation could lead to data breaches, reputational damage, and regulatory non-compliance.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jul 2025, 21:16 UTC

Technical details

References

Community reviews

Related threats