CVE-2025-5783VulnerabilityPublished 6 Jun 2025

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

Affects PHPGurukul Employee Record Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PHPGurukul Employee Record Management System	Affected =1.3	Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should immediately implement the following mitigations: 1) Restrict access to the /editmyexp.php endpoint by IP whitelisting or VPN-only access to limit exposure. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'emp3workduration' parameter. 3) Conduct thorough input validation and sanitization on all user inputs, especially parameters related to employee data, using parameterized queries or prepared statements if possible. 4) Monitor logs for unusual database queries or errors indicative of injection attempts. 5) Limit the database user privileges associated with the application to the minimum necessary, preventing unauthorized data manipulation. 6) Prepare for rapid patch deployment once the vendor releases an official fix. 7) Educate internal teams about the vulnerability and ensure incident response plans are updated to handle potential exploitation scenarios.

Description

A vulnerability, which was classified as critical, was found in PHPGurukul Employee Record Management System 1.3. This affects an unknown part of the file /editmyexp.php. The manipulation of the argument emp3workduration leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using PHPGurukul Employee Record Management System 1.3, this vulnerability poses a significant risk to employee data confidentiality and integrity. Exploitation could lead to unauthorized disclosure of personal employee information, modification of records, or deletion of critical HR data, disrupting business operations and potentially violating GDPR and other data protection regulations. The ability to remotely exploit the vulnerability without user interaction increases the attack surface and risk of automated attacks. Given the sensitivity of employee data, a successful attack could result in reputational damage, regulatory fines, and operational downtime. Furthermore, if the compromised system is integrated with other internal systems, the attacker could leverage the access to pivot and escalate privileges, amplifying the impact across the organization.

Summary

CVE-2025-5783 is a SQL Injection vulnerability identified in version 1.3 of the PHPGurukul Employee Record Management System, specifically within the /editmyexp.php file. The vulnerability arises from improper sanitization or validation of the 'emp3workduration' parameter, which allows an attacker to inject malicious SQL code. This flaw can be exploited remotely without any user interaction or authentication, as indicated by the CVSS vector (AV:N/AC:L/AT:N/UI:N/PR:L). The vulnerability impacts the confidentiality, integrity, and availability of the underlying database, potentially allowing attackers to read, modify, or delete sensitive employee data. Although the CVSS score is 5.3 (medium severity), the classification as critical in the description suggests that the vulnerability could have serious consequences if exploited in certain contexts. The exploit has been publicly disclosed but there are no known exploits currently observed in the wild. The vulnerability does not require user interaction but does require low privileges (PR:L), implying that an attacker might need to have some level of access, such as a low-privileged user account, to exploit it. The lack of patches or mitigation links indicates that the vendor has not yet released an official fix, increasing the urgency for organizations to implement compensating controls. SQL Injection vulnerabilities are among the most dangerous web application flaws because they can lead to full database compromise, data leakage, and potential lateral movement within the network.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 03:58 UTC

Technical details

References

Community reviews

Related threats