Cyber Resilience

CVE-2025-8134

LowPublic PoC

Published: 25 July 2025

Published
25 July 2025
Modified
29 April 2026
KEV Added
Patch
CVSS Score v4 2.1 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0031 54.7th percentile
Risk Priority 4 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2025-8134 is a low-severity Injection (CWE-74) vulnerability in Phpgurukul Bp Monitoring Management System. Its CVSS base score is 2.1 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 45.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).

Deeper analysis

CVE-2025-8134 is a critical SQL injection vulnerability (classified under CWE-74 and CWE-89) in PHPGurukul BP Monitoring Management System 1.0. The issue resides in unknown code within the file /bwdates-report-result.php, where manipulation of the fromdate and todate arguments triggers the injection. Published on 2025-07-25, it carries a CVSS v3.1 base score of 6.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

A remote attacker with low privileges can exploit this vulnerability over the network with little complexity. Successful exploitation enables limited impacts on confidentiality, integrity, and availability through SQL injection, allowing unauthorized data access, modification, or disruption within the affected application's database.

Advisories referenced in VulDB (ctiid.317530 and id.317530) and GitHub issues (LagonGit/ReportCVE #13 and #14) document the vulnerability, while the vendor site phpgurukul.com is listed as a resource. The exploit has been publicly disclosed, heightening the risk of widespread use. No specific patches or mitigations are detailed in the available information.

EU & UK References

Vulnerability details

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…

more

exploit has been disclosed to the public and may be used.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
T1213.006 Databases Collection
Adversaries may leverage databases to mine valuable information.
Why these techniques?

Unauthenticated SQL injection in public-facing PHP web application enables initial access via exploitation (T1190), abuse of server software components (T1505), and collection from databases (T1213.006).

CVEs Like This One

CVE-2025-2034Same vendor: Phpgurukul
CVE-2025-2663Same vendor: Phpgurukul
CVE-2025-2628Same vendor: Phpgurukul
CVE-2025-2739Same vendor: Phpgurukul
CVE-2025-2374Same vendor: Phpgurukul
CVE-2025-2640Same vendor: Phpgurukul
CVE-2025-2608Same vendor: Phpgurukul
CVE-2025-1580Same vendor: Phpgurukul
CVE-2025-2380Same vendor: Phpgurukul
CVE-2025-2058Same vendor: Phpgurukul

Affected Assets

phpgurukul
bp monitoring management system
1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation of fromdate/todate inputs in /bwdates-report-result.php to block SQL injection payloads.

prevent

Requires timely remediation of the known SQL injection flaw in the BP Monitoring Management System before public exploits are used.

prevent

Limits database privileges of the low-privilege account used by the web application, reducing impact of successful injection on confidentiality/integrity/availability.

References