Skip to main content
VulnerabilityPublished

CVE-2025-5248: PHPGurukul Company Visitor Management System · SQL Injection

Affects PHPGurukul Company Visitor Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 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
PHPGurukul Company Visitor Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

European organizations should immediately audit their environments to identify any deployments of PHPGurukul Company Visitor Management System version 1.0. As no official patches are currently available, organizations should implement the following specific mitigations: 1) Restrict network access to the visitor management system, limiting it to trusted internal networks or VPNs to reduce exposure. 2) Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting 'fromdate' and 'todate' parameters. 3) Conduct code reviews and apply manual input validation and parameterized queries in the affected PHP file if source code access is available. 4) Monitor logs for suspicious query patterns or unusual database errors indicative of injection attempts. 5) Plan for an upgrade or replacement of the vulnerable system with a patched or alternative solution as soon as a fix is released. 6) Educate IT and security teams about this vulnerability to ensure rapid response to any exploitation attempts.

Description

A vulnerability, which was classified as critical, was found in PHPGurukul Company Visitor Management System 1.0. Affected is an unknown function of the file /bwdates-reports-details.php. The manipulation of the argument fromdate/todate leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…