CVE-2025-13345: SQL Injection in SourceCodester Train Station Ticketing System
A security vulnerability has been detected in SourceCodester Train Station Ticketing System 1.0. Affected by this issue is some unknown functionality of the file /ajax.php?action=save_ticket. Such manipulation leads to sql injection. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.
AI Analysis
Technical Summary
CVE-2025-13345 identifies a SQL Injection vulnerability in the SourceCodester Train Station Ticketing System version 1.0. The vulnerability resides in the /ajax.php?action=save_ticket endpoint, where insufficient input validation allows an attacker to inject arbitrary SQL commands remotely. This flaw does not require authentication or user interaction, making it accessible to unauthenticated remote attackers. Exploiting this vulnerability could enable attackers to read, modify, or delete sensitive data within the backend database, potentially leading to unauthorized access to ticketing information, user data, or administrative credentials. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no exploits are currently known in the wild, the public disclosure increases the risk of exploitation by threat actors. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet, necessitating urgent remediation. The ticketing system is critical infrastructure for rail transport, and compromise could disrupt services or leak sensitive passenger data. The vulnerability highlights the need for secure coding practices such as parameterized queries and input sanitization in web applications handling critical transportation services.
Potential Impact
For European organizations, the impact of this SQL Injection vulnerability could be significant, especially for those operating or managing train station ticketing systems using the affected software. Successful exploitation could lead to unauthorized access to passenger data, including personal and payment information, resulting in privacy violations and regulatory non-compliance under GDPR. Data integrity could be compromised, allowing attackers to alter ticketing records, potentially causing financial losses or operational disruptions. Availability of ticketing services could also be affected if attackers execute destructive SQL commands or cause database outages, impacting customer experience and trust. Given the critical role of rail transport in Europe’s infrastructure and economy, such disruptions could have cascading effects on mobility and commerce. Additionally, attackers might leverage the vulnerability as a foothold for further network intrusion or lateral movement within organizational IT environments. The medium severity rating suggests moderate risk, but the ease of remote exploitation without authentication elevates the urgency for mitigation.
Mitigation Recommendations
To mitigate CVE-2025-13345, organizations should immediately conduct a thorough code review of the /ajax.php?action=save_ticket endpoint and any related database interaction code. Implement parameterized queries or prepared statements to prevent SQL Injection by ensuring user inputs are never directly concatenated into SQL commands. Input validation and sanitization should be enforced on all data received from clients. If available, apply official patches or updates from SourceCodester promptly. In the absence of patches, consider deploying Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL Injection attempts targeting this endpoint. Monitor database logs and application logs for unusual queries or error messages indicative of injection attempts. Restrict database user permissions to the minimum necessary to limit the impact of any potential exploitation. Additionally, conduct penetration testing and vulnerability scanning to verify the effectiveness of mitigations. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Belgium, Switzerland, Austria, Sweden
CVE-2025-13345: SQL Injection in SourceCodester Train Station Ticketing System
Description
A security vulnerability has been detected in SourceCodester Train Station Ticketing System 1.0. Affected by this issue is some unknown functionality of the file /ajax.php?action=save_ticket. Such manipulation leads to sql injection. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.
AI-Powered Analysis
Technical Analysis
CVE-2025-13345 identifies a SQL Injection vulnerability in the SourceCodester Train Station Ticketing System version 1.0. The vulnerability resides in the /ajax.php?action=save_ticket endpoint, where insufficient input validation allows an attacker to inject arbitrary SQL commands remotely. This flaw does not require authentication or user interaction, making it accessible to unauthenticated remote attackers. Exploiting this vulnerability could enable attackers to read, modify, or delete sensitive data within the backend database, potentially leading to unauthorized access to ticketing information, user data, or administrative credentials. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no exploits are currently known in the wild, the public disclosure increases the risk of exploitation by threat actors. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet, necessitating urgent remediation. The ticketing system is critical infrastructure for rail transport, and compromise could disrupt services or leak sensitive passenger data. The vulnerability highlights the need for secure coding practices such as parameterized queries and input sanitization in web applications handling critical transportation services.
Potential Impact
For European organizations, the impact of this SQL Injection vulnerability could be significant, especially for those operating or managing train station ticketing systems using the affected software. Successful exploitation could lead to unauthorized access to passenger data, including personal and payment information, resulting in privacy violations and regulatory non-compliance under GDPR. Data integrity could be compromised, allowing attackers to alter ticketing records, potentially causing financial losses or operational disruptions. Availability of ticketing services could also be affected if attackers execute destructive SQL commands or cause database outages, impacting customer experience and trust. Given the critical role of rail transport in Europe’s infrastructure and economy, such disruptions could have cascading effects on mobility and commerce. Additionally, attackers might leverage the vulnerability as a foothold for further network intrusion or lateral movement within organizational IT environments. The medium severity rating suggests moderate risk, but the ease of remote exploitation without authentication elevates the urgency for mitigation.
Mitigation Recommendations
To mitigate CVE-2025-13345, organizations should immediately conduct a thorough code review of the /ajax.php?action=save_ticket endpoint and any related database interaction code. Implement parameterized queries or prepared statements to prevent SQL Injection by ensuring user inputs are never directly concatenated into SQL commands. Input validation and sanitization should be enforced on all data received from clients. If available, apply official patches or updates from SourceCodester promptly. In the absence of patches, consider deploying Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL Injection attempts targeting this endpoint. Monitor database logs and application logs for unusual queries or error messages indicative of injection attempts. Restrict database user permissions to the minimum necessary to limit the impact of any potential exploitation. Additionally, conduct penetration testing and vulnerability scanning to verify the effectiveness of mitigations. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-11-18T06:53:19.261Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 691c6dffc50334694aba91c3
Added to database: 11/18/2025, 1:00:47 PM
Last enriched: 11/25/2025, 1:11:09 PM
Last updated: 1/8/2026, 6:09:56 AM
Views: 52
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0698: SQL Injection in code-projects Intern Membership Management System
MediumCVE-2026-0697: SQL Injection in code-projects Intern Membership Management System
MediumCVE-2026-22581
LowCVE-2026-22580
LowCVE-2026-22579
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.