CVE-2025-5658VulnerabilityPublished 5 Jun 2025

CVE-2025-5658: PHPGurukul Complaint Management System · SQL Injection

Affects PHPGurukul Complaint Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

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

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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 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-25.

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 Complaint Management System	Affected =2.0	Fixed in–

AI-suggested

1. Immediate mitigation should include restricting access to the /admin/updatecomplaint.php endpoint through network controls such as IP whitelisting, VPN access, or firewall rules to limit exposure to trusted administrators only. 2. Implement web application firewall (WAF) rules specifically designed to detect and block SQL injection patterns targeting the 'Status' parameter. 3. Conduct a thorough code review and apply input validation and parameterized queries or prepared statements to sanitize the 'Status' input, eliminating the injection vector. 4. If possible, upgrade to a patched version of the PHPGurukul Complaint Management System once released by the vendor. 5. Monitor logs for unusual database query patterns or repeated access attempts to the vulnerable endpoint to detect exploitation attempts early. 6. Educate administrators on secure password practices and multi-factor authentication to reduce the risk of compromised credentials facilitating exploitation. 7. As a longer-term measure, consider migrating to complaint management solutions with active security maintenance and community support to reduce exposure to unpatched vulnerabilities.

Description

A vulnerability classified as critical has been found in PHPGurukul Complaint Management System 2.0. Affected is an unknown function of the file /admin/updatecomplaint.php. The manipulation of the argument Status leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using PHPGurukul Complaint Management System 2.0, this vulnerability poses a significant risk to data confidentiality and integrity. Attackers exploiting this flaw could access sensitive complaint records, potentially exposing personal data protected under GDPR, leading to regulatory penalties and reputational damage. The ability to modify complaint statuses or records could disrupt business processes, affect customer service quality, and damage organizational credibility. Since the vulnerability is remotely exploitable without authentication, attackers could target exposed administrative interfaces directly, increasing the attack surface. This is particularly concerning for organizations with publicly accessible admin portals or insufficient network segmentation. Additionally, data tampering could impact audit trails and compliance reporting, complicating incident response and forensic investigations. The medium severity rating suggests that while the impact is not catastrophic, the risk is non-negligible and warrants prompt attention to prevent escalation or chaining with other vulnerabilities.

Summary

CVE-2025-5658 is a SQL Injection vulnerability identified in version 2.0 of the PHPGurukul Complaint Management System, specifically within the /admin/updatecomplaint.php file. The vulnerability arises due to improper sanitization or validation of the 'Status' parameter, which is manipulated by an attacker to inject malicious SQL code. This injection flaw allows an attacker to interfere with the queries executed by the backend database, potentially enabling unauthorized data access, modification, or deletion. The vulnerability is remotely exploitable without requiring user interaction or authentication, increasing its risk profile. The CVSS 4.0 base score is 5.3, indicating a medium severity level, primarily because it requires low privileges (PR:L) but no user interaction (UI:N) and has limited impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The vulnerability has been publicly disclosed, but no known exploits are currently observed in the wild. However, the public disclosure increases the risk of exploitation attempts. The lack of available patches or mitigations from the vendor at this time further exacerbates the threat. Given the nature of complaint management systems, which often handle sensitive user or customer data, exploitation could lead to unauthorized data exposure or manipulation, undermining trust and compliance with data protection regulations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 05:55 UTC

Technical details

References

Community reviews

Related threats