Skip to main content
VulnerabilityPublished

CVE-2025-9302: PHPGurukul User Management System · SQL Injection

Affects PHPGurukul User Management SystemSource CVE Database V5

0

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 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 37% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
PHPGurukul User Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

  1. Immediate mitigation involves implementing input validation and parameterized queries or prepared statements in the /signup.php script to prevent SQL injection.
  2. Organizations should audit their PHPGurukul User Management System installations to identify affected versions and isolate vulnerable instances.
  3. If vendor patches are unavailable, consider applying community-developed fixes or employing Web Application Firewalls (WAFs) with specific SQL injection detection rules to block malicious payloads targeting the 'emailid' parameter.
  4. Conduct thorough code reviews and penetration testing focused on input handling in user registration and management modules.
  5. Monitor logs for suspicious activities related to signup requests and unusual database errors.
  6. As a longer-term solution, upgrade to a more secure user management platform or newer versions once patches are released.
  7. Implement strict access controls and database permissions to limit the impact of any successful injection.
  8. Educate developers on secure coding practices to prevent similar vulnerabilities in future development.

Description

A vulnerability was identified in PHPGurukul User Management System 1.0. This vulnerability affects unknown code of the file /signup.php. Such manipulation of the argument emailid leads to sql injection. The attack can be executed remotely. The exploit is publicly available and might be used.

References

Community reviews

Loading reviews…