CVE-2025-26199VulnerabilityPublished 18 Jun 2025Updated 20 Jun 2025

CVE-2025-26199: CloudClassroom-PHP-Project · n/a

Affects CloudClassroom-PHP-ProjectSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.8Critical

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 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
GitHubtansique-17/CloudClassroom-PHP-Project`pkg:github/tansique-17/CloudClassroom-PHP-Project`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate the risks associated with CVE-2025-26199, organizations should take immediate and specific actions beyond generic security hygiene: 1) Apply any available patches or updates from the CloudClassroom PHP Project maintainers as soon as they are released. In the absence of official patches, consider temporarily disabling the affected password submission functionality or restricting access to the application via network segmentation and firewall rules. 2) Implement Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting password submission endpoints, focusing on patterns indicative of code injection attempts. 3) Enforce HTTPS to protect data in transit and prevent interception of cleartext passwords. 4) Conduct thorough code reviews and penetration testing on the password handling modules to identify and remediate insecure coding practices, such as lack of input validation and sanitization. 5) Employ multi-factor authentication (MFA) to reduce the impact of credential compromise. 6) Monitor logs and network traffic for unusual activity related to authentication attempts or code execution anomalies. 7) Educate administrators and users about the risks and signs of exploitation to enable rapid detection and response. 8) Consider migrating to alternative, more secure e-learning platforms if timely remediation is not feasible.

Description

CloudClassroom-PHP-Project v1.0 is affected by an insecure credential transmission vulnerability. The application transmits passwords over unencrypted HTTP during the login process, exposing sensitive credentials to potential interception by network-based attackers. A remote attacker with access to the same network (e.g., public Wi-Fi or compromised router) can capture login credentials via Man-in-the-Middle (MitM) techniques. If the attacker subsequently uses the credentials to log in and exploit administrative functions (e.g., file upload), this may lead to remote code execution depending on the environment.

Impact

For European organizations, the exploitation of CVE-2025-26199 could have severe consequences. Educational institutions and e-learning providers using the CloudClassroom PHP Project may face unauthorized access to sensitive student and staff information, including personal data and credentials. The arbitrary code execution capability could allow attackers to deploy malware, ransomware, or pivot to other internal systems, disrupting educational services and causing significant operational downtime. Confidentiality breaches could lead to violations of GDPR regulations, resulting in legal penalties and reputational damage. Integrity of educational content and user data could be compromised, undermining trust in the platform. Availability may also be affected if attackers disable or manipulate the service. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially in environments where patching and security monitoring are insufficient. Furthermore, the lack of encryption in password handling could expose credentials to interception or replay attacks, compounding the risk of broader account compromise.

Summary

CVE-2025-26199 is a vulnerability identified in the CloudClassroom PHP Project version 1.0. The core issue involves the handling of password submissions in cleartext, which allows a remote attacker to execute arbitrary code on the affected system. Specifically, the vulnerability arises because the application processes passwords without adequate encryption or secure handling, enabling attackers to inject malicious payloads during the password submission process. This flaw can be exploited remotely, without requiring prior authentication or user interaction, making it particularly dangerous. The lack of encryption or secure validation in the password handling mechanism means that an attacker can craft specially designed requests that trigger code execution on the server, potentially leading to full system compromise. Although no known exploits have been reported in the wild yet, the vulnerability’s nature suggests a high risk of exploitation once publicly disclosed. The absence of a CVSS score indicates that the vulnerability is newly published and has not yet undergone formal severity assessment. The vulnerability affects CloudClassroom PHP Project v1.0, a web-based educational platform built on PHP, which is commonly used for online learning environments. Given the typical deployment of such platforms, the vulnerability could impact web servers hosting the application, potentially exposing sensitive user data and administrative controls to attackers.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Jun 2025, 19:46 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats