VulnerabilityPublished 4 Jun 2025Updated 6 Feb 2026

CVE-2025-5553: PHPGurukul Rail Pass Management System · SQL Injection

Affects PHPGurukul Rail Pass Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% 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 4 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 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 or the CVSS exploit maturity 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 Rail Pass Management System	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately conduct a thorough security review of the PHPGurukul Rail Pass Management System, focusing on the /download-pass.php endpoint. Specific mitigations include: 1) Implementing parameterized queries or prepared statements to prevent SQL injection; 2) Applying rigorous input validation and sanitization on all user-supplied data, especially the 'searchdata' parameter; 3) Restricting database user permissions to the minimum necessary to limit potential damage; 4) Monitoring database logs and web application logs for anomalous queries or access patterns indicative of injection attempts; 5) If possible, upgrading to a patched version or applying vendor-provided fixes once available; 6) Employing Web Application Firewalls (WAFs) with rules targeting SQL injection signatures to provide an additional layer of defense; 7) Conducting penetration testing and code audits to identify and remediate similar vulnerabilities elsewhere in the application; 8) Ensuring incident response plans are updated to address potential exploitation scenarios. These steps go beyond generic advice by focusing on the specific vulnerable component and operational context.

Description

A vulnerability classified as critical was found in PHPGurukul Rail Pass Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /download-pass.php. The manipulation of the argument searchdata leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, especially those involved in rail transport and ticketing, this vulnerability poses a risk to the confidentiality and integrity of passenger data and operational databases. Exploitation could lead to unauthorized disclosure of sensitive personal and travel information, manipulation of ticketing records, or denial of service through database corruption. This could result in regulatory penalties under GDPR due to data breaches, reputational damage, and operational disruptions affecting customer trust and revenue. Given the critical nature of transportation infrastructure, successful exploitation might also have cascading effects on service availability and safety. The medium CVSS score reflects moderate impact, but the ease of remote exploitation without authentication elevates the threat level. European rail operators using PHPGurukul's system or similar legacy software are particularly vulnerable, potentially exposing critical infrastructure to cyberattacks.

Summary

CVE-2025-5553 is a critical SQL Injection vulnerability identified in version 1.0 of the PHPGurukul Rail Pass Management System, specifically within the /download-pass.php script. The vulnerability arises from improper sanitization of the 'searchdata' parameter, which is directly incorporated into SQL queries without adequate validation or parameterization. This flaw enables remote attackers to inject arbitrary SQL commands, potentially allowing unauthorized access to sensitive data, modification of database contents, or disruption of service. The attack vector is network-based (AV:N), requires no privileges (PR:N), no user interaction (UI:N), and no authentication, making exploitation straightforward. The CVSS 4.0 base score is 6.9, reflecting medium severity due to limited impact on confidentiality, integrity, and availability, but ease of exploitation. Although no known exploits have been observed in the wild, the public disclosure of the vulnerability increases the risk of exploitation. The lack of patches or vendor advisories necessitates immediate attention from users of this software. The vulnerability is particularly concerning for organizations managing rail pass data, as it could expose passenger information or disrupt ticketing operations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Feb 2026, 08:08 UTC

Technical details

References

Community reviews

Related threats