CVE-2025-12873VulnerabilityPublished 7 Nov 2025

CVE-2025-12873: Campcodes School File Management · SQL Injection

Affects Campcodes School File ManagementSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% 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 7 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
Campcodes School File Management	Affected =1.0	Fixed in–

AI-suggested

1. Immediately restrict access to the /admin/update_user.php endpoint using network segmentation, VPNs, or IP whitelisting to limit exposure to authorized personnel only. 2. Implement strong authentication mechanisms, such as multi-factor authentication, to reduce the risk of credential compromise. 3. Apply input validation and parameterized queries in the application code to prevent SQL injection, even if patches are not yet available. 4. Monitor logs for unusual activity related to user_id parameter manipulation or unauthorized access attempts. 5. Engage with the vendor to obtain and apply security patches as soon as they are released. 6. Conduct security awareness training for administrators to recognize phishing or social engineering attempts that could lead to privilege escalation. 7. Regularly audit user privileges to ensure only necessary personnel have admin access. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this endpoint. 9. Maintain up-to-date backups of critical data to enable recovery in case of data tampering or deletion.

Description

A security flaw has been discovered in Campcodes School File Management 1.0. This affects an unknown part of the file /admin/update_user.php. Performing manipulation of the argument user_id results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be exploited.

Impact

For European organizations, particularly educational institutions using Campcodes School File Management 1.0, this vulnerability poses a risk of unauthorized access to sensitive student and administrative data. Exploitation could lead to data breaches, manipulation of user records, and disruption of school operations. The impact on confidentiality and integrity is moderate due to the high privilege requirement, but the potential exposure of personal data conflicts with GDPR mandates, increasing regulatory and reputational risks. Availability impact is low but possible if attackers modify or delete critical data. The vulnerability could also serve as a foothold for further attacks within the network if exploited by insiders or through compromised credentials. European schools with limited cybersecurity resources may be particularly vulnerable. The public availability of exploit code raises the likelihood of opportunistic attacks, especially in countries with widespread use of this software or similar educational management systems.

Summary

CVE-2025-12873 is a SQL injection vulnerability identified in Campcodes School File Management version 1.0, affecting the /admin/update_user.php endpoint. The vulnerability arises from improper sanitization of the user_id parameter, allowing an attacker to inject malicious SQL queries remotely. The attack vector is network-based with low attack complexity, but requires high privileges (PR:H), meaning the attacker must have some level of authenticated access to the admin interface. No user interaction is needed, and the vulnerability impacts confidentiality, integrity, and availability at a low level. The CVSS 4.0 vector indicates no scope change and no privileges required for attack initiation, but the high privilege requirement limits exploitation to authorized users or compromised accounts. Although no known exploits are currently active in the wild, the public release of exploit code increases the risk of future attacks. The vulnerability could allow unauthorized data retrieval, modification, or deletion within the school management system, potentially exposing sensitive student and staff information. The lack of vendor patches at the time of disclosure necessitates immediate mitigation through access restrictions and input validation. Given the nature of the product, educational institutions using Campcodes software are the primary targets, with potential for broader impact if integrated with other systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Nov 2025, 18:21 UTC

Technical details

References

Community reviews

Related threats