CVE-2026-2058VulnerabilityPublished 6 Feb 2026Updated 23 Feb 2026

CVE-2026-2058: mathurvishal CloudClassroom-PHP-Project · SQL Injection

Affects mathurvishal CloudClassroom-PHP-ProjectSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% 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 6 Feb 2026
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

Affected software

Product	Affected	Fixed in
mathurvishalCloudClassroom-PHP-Project	Affected =5dadec098bfbbf3300d60c3494db3fb95b66e7be	Fixed in–

AI-suggested

Organizations should immediately audit their CloudClassroom-PHP-Project deployments for the presence of the vulnerable /postquerypublic.php file and the gnamex parameter. Until an official patch is released, implement the following mitigations: 1) Apply strict input validation and sanitization on all user-supplied parameters, especially gnamex, to reject or escape SQL meta-characters. 2) Refactor database queries to use prepared statements with parameterized queries to eliminate direct concatenation of user input. 3) Employ web application firewalls (WAFs) with SQL injection detection rules to block malicious payloads targeting this vulnerability. 4) Monitor logs for suspicious query patterns or repeated access to /postquerypublic.php with unusual parameter values. 5) Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. 6) Consider isolating the application environment and enforcing network segmentation to reduce exposure. 7) Stay alert for vendor updates or community patches and apply them promptly once available. 8) Educate developers on secure coding practices to prevent similar vulnerabilities in future releases.

Description

A flaw has been found in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file /postquerypublic.php of the component Post Query Details Page. This manipulation of the argument gnamex causes sql injection. The attack is possible to be carried out remotely. The exploit has been published and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SQL injection vulnerability allows remote attackers to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized data disclosure, data manipulation, or deletion. This can compromise sensitive educational data, user credentials, or administrative information stored in the CloudClassroom system. The integrity of the application and its data can be undermined, affecting trust and operational continuity. Availability may also be impacted if attackers execute destructive queries or cause database errors. Organizations relying on this software for educational or training purposes may face data breaches, regulatory penalties, and reputational damage. The lack of vendor response and patches increases the window of exposure, making timely mitigation critical. Since the exploit is publicly available, the likelihood of attacks increases, especially against unpatched or poorly secured deployments.

Summary

CVE-2026-2058 identifies a SQL injection vulnerability in the CloudClassroom-PHP-Project developed by mathurvishal. The vulnerability resides in the /postquerypublic.php file, specifically in the handling of the gnamex parameter within the Post Query Details Page component. An attacker can remotely inject malicious SQL code through this parameter, manipulating backend database queries without requiring authentication or user interaction. This can lead to unauthorized data access, modification, or deletion, compromising the confidentiality, integrity, and availability of the affected system's data. The project uses a rolling release strategy, making it difficult to pinpoint exact affected versions beyond the given commit hash. The vendor has not responded to disclosure attempts, and no official patches are available. Although no widespread exploitation has been reported, published exploits increase the risk of attacks. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges or user interaction required, and impacts on confidentiality, integrity, and availability at a low level. This vulnerability highlights the importance of secure input validation and parameterized queries in PHP web applications.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:08 UTC

Technical details

References

Community reviews

Related threats