CVE-2025-13270VulnerabilityPublished 17 Nov 2025Updated 24 Feb 2026

CVE-2025-13270: Campcodes School Fees Payment Management System · SQL Injection

Affects Campcodes School Fees Payment Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 17 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 Fees Payment Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-13270 effectively, organizations should implement the following specific measures: 1) Apply official patches or updates from Campcodes as soon as they become available to address the vulnerability at the source. 2) In the absence of patches, implement immediate input validation and sanitization on the 'ID' parameter in the /ajax.php?action=save_course endpoint to prevent malicious SQL code injection. 3) Refactor the vulnerable code to use parameterized queries or prepared statements, eliminating direct concatenation of user input into SQL commands. 4) Restrict access to the vulnerable endpoint by enforcing strict authentication and authorization controls, ensuring only trusted users with appropriate privileges can invoke it. 5) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting this endpoint. 6) Conduct comprehensive security audits and code reviews of the payment management system to identify and remediate similar injection flaws. 7) Monitor logs and network traffic for anomalous activities indicative of SQL injection attempts or exploitation. 8) Educate system administrators and developers on secure coding practices and the importance of least privilege principles. 9) Consider network segmentation to isolate the payment system backend from less trusted network zones, reducing attack surface. 10) Regularly back up critical databases and verify restoration procedures to minimize impact from potential data corruption or deletion. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and operational context of the Campcodes system.

Description

A vulnerability was found in Campcodes School Fees Payment Management System 1.0. This affects an unknown function of the file /ajax.php?action=save_course. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used.

Impact

The potential impact of CVE-2025-13270 is significant for organizations using the Campcodes School Fees Payment Management System, especially educational institutions managing sensitive financial and student data. Successful exploitation could lead to unauthorized disclosure of confidential information such as student identities, payment records, and financial transactions, resulting in privacy violations and regulatory non-compliance. Data integrity could be compromised, allowing attackers to alter payment records or course information, potentially causing financial discrepancies or administrative confusion. Availability impacts may include disruption of payment processing services, leading to operational downtime and reputational damage. Financial fraud risks increase if attackers manipulate payment data or redirect funds. The requirement for low privileges to exploit the vulnerability suggests that attackers may chain this with other vulnerabilities or social engineering to gain initial access, amplifying the threat. Globally, institutions relying on this software without timely mitigation are exposed to data breaches, financial loss, and operational disruption. The public disclosure of exploit code increases the likelihood of opportunistic attacks, especially from less sophisticated threat actors. The medium severity rating indicates that while the threat is not critical, the sensitive nature of the affected data and the potential for chained attacks elevate the risk profile. Organizations failing to address this vulnerability may face legal liabilities, loss of stakeholder trust, and increased incident response costs.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats