Skip to main content
CVE-2025-8134VulnerabilityPublished

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

Affects PHPGurukul BP Monitoring Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 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 42% 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 25 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHublagongit/ReportCVEpkg:github/lagongit/ReportCVEOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately audit their use of PHPGurukul BP Monitoring Management System to identify any instances of version 1.0 deployment. Since no official patches are currently available, organizations should implement the following specific mitigations: 1) Apply strict input validation and sanitization on the 'fromdate' and 'todate' parameters at the web application firewall (WAF) or reverse proxy level to block SQL injection payloads. 2) Employ parameterized queries or prepared statements in the application code if source code access is available, to prevent injection. 3) Restrict database user privileges associated with the application to the minimum necessary, limiting the impact of any injection. 4) Monitor database logs and application logs for suspicious query patterns or anomalies related to these parameters. 5) Isolate the BP Monitoring Management System within a segmented network zone with limited external access to reduce exposure. 6) Consider deploying runtime application self-protection (RASP) tools to detect and block injection attempts in real time. 7) Plan for an upgrade or migration to a patched or alternative solution as soon as a fix becomes available. These measures go beyond generic advice by focusing on immediate protective controls and architectural adjustments tailored to this specific vulnerability.

Description

A vulnerability classified as critical was found in PHPGurukul BP Monitoring Management System 1.0. This vulnerability affects unknown code of the file /bwdates-report-result.php. The manipulation of the argument fromdate/todate 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…