CVE-2025-6341VulnerabilityPublished 20 Jun 2025

CVE-2025-6341: code-projects School Fees Payment System · Cross-Site Request Forgery

Affects code-projects School Fees Payment 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.2% chance of exploitation in 30 days – higher than 17% 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 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
code-projects School Fees Payment System	Affected =1.0	Fixed in–

AI-suggested

1. Implement robust anti-CSRF protections in the School Fees Payment System, including the use of synchronizer tokens or double-submit cookies to validate the legitimacy of requests. 2. Enforce strict SameSite cookie attributes (preferably 'Strict' or 'Lax') to limit cross-origin requests. 3. Educate users on phishing and social engineering risks to reduce the chance of inadvertent interaction with malicious links. 4. Monitor web server logs and application behavior for unusual or unauthorized transaction requests that could indicate exploitation attempts. 5. Restrict the system's exposure by limiting access to trusted networks or VPNs where feasible. 6. If possible, upgrade to a patched version once available or apply vendor-recommended workarounds. 7. Conduct regular security assessments and penetration testing focusing on CSRF and other web vulnerabilities. 8. Implement multi-factor authentication (MFA) to add an additional layer of user verification, reducing the impact of session hijacking or unauthorized actions. 9. Segregate payment processing functions with additional confirmation steps or manual review to detect anomalous transactions. 10. Maintain up-to-date backups of payment data to enable recovery in case of data manipulation.

Description

A vulnerability classified as problematic was found in code-projects School Fees Payment System 1.0. This vulnerability affects unknown code. The manipulation leads to cross-site request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, especially educational institutions and school administrations using the code-projects School Fees Payment System, this vulnerability poses a risk of unauthorized manipulation of payment transactions. Attackers could exploit this flaw to initiate fraudulent fee payments, alter payment statuses, or disrupt normal financial operations without the victim's consent. While the direct impact on confidentiality and availability is minimal, the integrity of financial data and transaction records could be compromised, leading to financial losses, reputational damage, and administrative burdens. Given the medium severity and requirement for user interaction, the threat is more pronounced in environments where users frequently access the payment system via web browsers and may be susceptible to social engineering attacks such as phishing. The lack of known active exploits reduces immediate risk but the public disclosure increases the likelihood of future exploitation attempts. Organizations may also face regulatory scrutiny under GDPR if financial data integrity is compromised or if the incident leads to broader data protection concerns.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats