Skip to main content
CVE-2025-5856VulnerabilityPublished

CVE-2025-5856: PHPGurukul BP Monitoring Management System · SQL Injection

Affects PHPGurukul BP Monitoring Management SystemSource CVE Database V5

0

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jun 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-26.

What to do

Affected software

ProductAffectedFixed in
PHPGurukul BP Monitoring Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

Organizations should immediately audit their use of the PHPGurukul BP Monitoring Management System version 1.0 and identify any deployments. Input validation and sanitization should be enforced at the application level, ideally by modifying the source code to use parameterized queries or prepared statements instead of directly embedding user input in SQL commands. Network segmentation and strict access controls should be applied to limit exposure of the vulnerable system to only trusted internal networks. Regular database backups should be maintained to enable recovery in case of data corruption. Organizations should also monitor logs for unusual query patterns or errors indicative of SQL injection attempts. Finally, they should engage with PHPGurukul or the software vendor for updates or patches and plan for an upgrade or replacement of the vulnerable system.

Description

A vulnerability has been found in PHPGurukul BP Monitoring Management System 1.0 and classified as critical. This vulnerability affects unknown code of the file /registration.php. The manipulation of the argument emailid leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…