Skip to main content
VulnerabilityPublished Updated

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

Affects PHPGurukul User Management SystemSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 4.0 base score
5.3Medium
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:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Sep 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. Apply vendor patches immediately once available to address the SQL injection vulnerability in the /admin/edit-user-profile.php file.
  2. Until patches are released, implement strict input validation and sanitization on the uid parameter, ensuring only expected numeric or alphanumeric values are accepted.
  3. Employ parameterized queries or prepared statements in the application code to prevent SQL injection.
  4. Restrict access to the /admin/edit-user-profile.php endpoint to trusted administrators and limit exposure to the internet via network segmentation or firewall rules.
  5. Monitor logs for suspicious activities related to the uid parameter, such as unexpected SQL syntax or error messages indicating injection attempts.
  6. Conduct regular security assessments and code reviews focusing on input handling in user management modules.
  7. Educate administrators about the risks and signs of SQL injection attacks to enable prompt detection and response.
  8. Consider deploying Web Application Firewalls (WAFs) with rules tuned to detect and block SQL injection payloads targeting this endpoint.

Description

A security flaw has been discovered in PHPGurukul User Management System 1.0. Affected is an unknown function of the file /admin/edit-user-profile.php. The manipulation of the argument uid results in sql injection. The attack may be performed from remote. The exploit has been released to the public and may be exploited.

References

Community reviews

Loading reviews…