Skip to main content
CVE-2025-7543VulnerabilityPublished Updated

CVE-2025-7543: PHPGurukul User Registration & Login and User Management System · SQL Injection

Affects PHPGurukul User Registration & Login and User Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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 38% 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 13 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
PHPGurukul User Registration & Login and User Management SystemAffected
  • =3.3
Fixed in–

AI-suggested

1. Immediate patching or upgrading to a fixed version of the PHPGurukul system is the most effective mitigation; if unavailable, apply virtual patching via Web Application Firewalls (WAF) to block malicious payloads targeting the 'ID' parameter in /admin/manage-users.php. 2. Restrict access to the administrative interface by IP whitelisting or VPN-only access to reduce exposure to external attackers. 3. Implement strict input validation and parameterized queries in the application code to prevent SQL injection attacks. 4. Conduct thorough security audits and code reviews focusing on all user input handling in the user management modules. 5. Monitor logs for unusual database queries or repeated failed attempts to access administrative functions. 6. Employ database-level access controls to limit the impact of any successful injection, such as using least privilege accounts for the web application. 7. Educate system administrators and developers about the risks of SQL injection and the importance of secure coding practices.

Description

A vulnerability was found in PHPGurukul User Registration & Login and User Management System 3.3. It has been classified as critical. This affects an unknown part of the file /admin/manage-users.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…