CVE-2025-5231VulnerabilityPublished 27 May 2025

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

Affects PHPGurukul Company Visitor Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 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 26 Oct 2026.

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 Company Visitor Management System	Affected =1.0	Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should immediately implement the following specific mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the /forgot-password.php endpoint, especially focusing on the 'email' parameter. 2) Conduct immediate code audits and apply input validation and parameterized queries or prepared statements for all database interactions, particularly for the vulnerable script. 3) Restrict database user permissions to the minimum necessary, preventing unauthorized data manipulation even if injection occurs. 4) Monitor logs for unusual query patterns or repeated failed password reset attempts that may indicate exploitation attempts. 5) Isolate the visitor management system network segment to limit lateral movement in case of compromise. 6) Consider temporary disabling or restricting access to the forgot-password functionality until a secure fix is deployed. 7) Engage with PHPGurukul for timely patch releases and subscribe to vulnerability advisories for updates.

Description

A vulnerability classified as critical was found in PHPGurukul Company Visitor Management System 1.0. This vulnerability affects unknown code of the file /forgot-password.php. The manipulation of the argument email leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the PHPGurukul Company Visitor Management System 1.0, this vulnerability poses significant risks. Visitor management systems often store sensitive personal data, including visitor identities, contact details, visit times, and potentially access credentials or security clearances. Exploitation could lead to data breaches violating GDPR and other privacy regulations, resulting in legal penalties and reputational damage. Additionally, attackers could manipulate visitor logs to cover unauthorized physical access or disrupt operational continuity. The ability to execute SQL injection remotely without authentication amplifies the threat, potentially allowing attackers to pivot into other internal systems if the visitor management system database is interconnected. This could impact organizations in sectors with high security requirements such as government, finance, healthcare, and critical infrastructure within Europe.

Summary

CVE-2025-5231 is a critical SQL Injection vulnerability identified in version 1.0 of the PHPGurukul Company Visitor Management System, specifically within the /forgot-password.php script. The vulnerability arises due to improper sanitization or validation of the 'email' parameter, which is directly incorporated into an SQL query without adequate escaping or parameterization. This flaw allows an unauthenticated remote attacker to inject malicious SQL code, potentially manipulating the backend database. Exploitation could lead to unauthorized data access, modification, or deletion, compromising the confidentiality, integrity, and availability of the system's data. The vulnerability does not require any authentication or user interaction, making it easily exploitable remotely. Although the CVSS 4.0 score is 6.9 (medium severity), the nature of SQL injection vulnerabilities often implies a higher risk, especially if the database contains sensitive visitor or company information. The vulnerability disclosure is public, but no known exploits have been reported in the wild yet. The lack of available patches or mitigations from the vendor increases the urgency for organizations to implement compensating controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 10:46 UTC

Technical details

References

Community reviews

Related threats