CVE-2025-11660VulnerabilityPublished 13 Oct 2025Updated 14 Oct 2025

CVE-2025-11660: ProjectsAndPrograms School Management System · Unrestricted Upload

Affects ProjectsAndPrograms School Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% 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 13 Oct 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-26.

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

AI-suggested

To mitigate CVE-2025-11660, organizations should immediately audit and restrict file upload functionalities within the ProjectsAndPrograms School Management System. Specific steps include: 1) Implement strict server-side validation of uploaded files, including file type, size, and content inspection to prevent malicious payloads. 2) Employ allowlists for acceptable file extensions and reject all others. 3) Use secure storage locations for uploads, segregated from executable directories to prevent execution of uploaded files. 4) Apply web application firewalls (WAF) with rules to detect and block suspicious upload attempts. 5) Monitor logs for unusual upload activity or access patterns. 6) Engage with the vendor or community to identify patches or updates addressing this vulnerability, despite the rolling release model. 7) If patches are unavailable, consider temporary disabling or restricting the upload feature until a fix is applied. 8) Educate system administrators on the risks and signs of exploitation. 9) Regularly back up critical data and test restoration procedures to minimize impact of potential attacks. 10) Conduct penetration testing focusing on file upload mechanisms to validate defenses.

Description

A vulnerability has been found in ProjectsAndPrograms School Management System up to 6b6fae5426044f89c08d0dd101c7fa71f9042a59. Affected by this issue is some unknown functionality of the file /assets/uploadSllyabus.php. Such manipulation of the argument File leads to unrestricted upload. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable.

Impact

For European organizations, especially educational institutions using the ProjectsAndPrograms School Management System, this vulnerability poses significant risks. Successful exploitation could lead to unauthorized access to sensitive student records, administrative data, and internal communications, impacting confidentiality. Attackers could also modify or delete data, affecting data integrity, or deploy malware that disrupts system availability, causing operational downtime. Given the remote and unauthenticated nature of the exploit, attackers can target these systems en masse, increasing the risk of widespread compromise. The rolling release nature of the software complicates patch management, potentially delaying remediation and prolonging exposure. Additionally, educational institutions are often targeted for espionage or ransomware attacks, making this vulnerability a potential vector for such threats. The impact extends beyond individual organizations to affect trust in educational services and compliance with data protection regulations such as GDPR.

Summary

CVE-2025-11660 is a vulnerability identified in the ProjectsAndPrograms School Management System, specifically in the file /assets/uploadSllyabus.php. The issue arises from improper handling of the 'File' argument, allowing attackers to upload files without restrictions. This unrestricted upload vulnerability can be exploited remotely without any authentication or user interaction, making it highly accessible to attackers. The uploaded files could include malicious scripts or executables, potentially enabling remote code execution, data exfiltration, or disruption of services. The product uses a rolling release model, complicating version tracking and patch management, as affected or fixed versions are not clearly delineated. The CVSS 4.0 score of 6.9 (medium severity) reflects the network attack vector, low complexity, no privileges or user interaction required, and limited impact on confidentiality, integrity, and availability. Although no exploits are currently known in the wild, the public disclosure of the vulnerability increases the likelihood of exploitation attempts. The vulnerability is particularly concerning for educational institutions relying on this system to manage sensitive student and administrative data, as exploitation could lead to unauthorized access or system compromise.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 21 Oct 2025, 00:31 UTC

Technical details

References

Community reviews

Related threats