VulnerabilityPublished 24 Jun 2025

CVE-2025-6569: code-projects School Fees Payment System · Cross-site Scripting

Affects code-projects School Fees Payment SystemSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 33% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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
code-projects School Fees Payment System	Affected =1.0	Fixed in–

AI-suggested

Immediate implementation of input validation and output encoding: Sanitize all user inputs on the server side for the affected parameters (sname, contact, about, emailid, transcation_remark) to neutralize malicious scripts. Use context-appropriate encoding (e.g., HTML entity encoding) before reflecting inputs back to the client.
Employ Content Security Policy (CSP): Configure CSP headers to restrict the execution of inline scripts and loading of resources from untrusted sources, mitigating the impact of XSS payloads.
Use HTTP-only and Secure cookies: Ensure session cookies are marked HTTP-only and Secure to reduce the risk of session hijacking via script access.
Monitor and restrict URL parameters: Implement server-side checks to detect and block suspicious or malformed input patterns in URL parameters.
Educate users: Inform users about the risks of clicking unknown links and encourage cautious behavior when interacting with the payment system.
Isolate the payment system: If possible, restrict access to the payment system to authenticated users or trusted networks until a patch is available.
Regularly update and patch: Engage with the vendor or community to obtain patches or updates addressing this vulnerability.
Implement Web Application Firewall (WAF): Deploy a WAF with rules to detect and block common XSS attack patterns targeting the affected parameters.
Conduct security testing: Perform penetration testing and code reviews focusing on input handling in /student.php and related modules to identify and remediate similar vulnerabilities.

Description

A vulnerability classified as problematic was found in code-projects School Fees Payment System 1.0. Affected by this vulnerability is an unknown functionality of the file /student.php. The manipulation of the argument sname/contact/about/emailid/transcation_remark leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the code-projects School Fees Payment System 1.0, this XSS vulnerability could lead to several adverse impacts. Attackers could exploit the vulnerability to execute malicious scripts in the browsers of students, parents, or administrative staff interacting with the system. This could result in session hijacking, enabling attackers to impersonate legitimate users and potentially access sensitive student or payment information. Additionally, attackers could perform phishing attacks by injecting fake login forms or redirecting users to malicious websites, undermining trust in the payment system. While the vulnerability does not directly compromise system availability or confidentiality at the server level, the integrity of user interactions and data could be compromised, leading to reputational damage and potential regulatory scrutiny under GDPR if personal data is mishandled. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially if the system is publicly accessible. Given that school fee payment systems are critical for educational institutions, disruption or compromise could affect operational continuity and financial transactions. The medium severity rating suggests that while the threat is not critical, it should be addressed promptly to prevent exploitation and protect stakeholders.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Jun 2025, 15:26 UTC

Technical details

References

Community reviews

Related threats