Skip to main content
VulnerabilityPublished

CVE-2025-5212: PHPGurukul Employee Record Management System · SQL Injection

Affects PHPGurukul Employee Record Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 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 43% 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 26 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 Employee Record Management SystemAffected
  • =1.3
Fixed in–

AI-suggested

Organizations should immediately audit their use of PHPGurukul Employee Record Management System version 1.3 and restrict access to the /admin/editempexp.php endpoint to trusted internal networks only. Implementing Web Application Firewalls (WAFs) with SQL Injection detection rules can provide temporary protection against exploitation attempts. Input validation and parameterized queries should be enforced in the application code to prevent injection attacks; if source code access is available, developers must sanitize and validate the 'emp1name' parameter rigorously. Monitoring database logs for suspicious queries and unusual access patterns is recommended to detect potential exploitation. Organizations should engage with the vendor or community to obtain patches or updates and plan for an upgrade to a fixed version once available. Additionally, applying the principle of least privilege to database accounts used by the application can limit the damage from a successful injection. Regular security assessments and penetration testing focused on SQL Injection vectors should be conducted to ensure ongoing protection.

Description

A vulnerability was found in PHPGurukul Employee Record Management System 1.3. It has been classified as critical. Affected is an unknown function of the file /admin/editempexp.php. The manipulation of the argument emp1name 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…