Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13347: SQL Injection in SourceCodester Train Station Ticketing System

0
Medium
VulnerabilityCVE-2025-13347cvecve-2025-13347
Published: Tue Nov 18 2025 (11/18/2025, 13:02:05 UTC)
Source: CVE Database V5
Vendor/Project: SourceCodester
Product: Train Station Ticketing System

Description

A flaw has been found in SourceCodester Train Station Ticketing System 1.0. This vulnerability affects unknown code of the file /ajax.php?action=save_user. Executing manipulation of the argument Username can lead to sql injection. The attack may be launched remotely. The exploit has been published and may be used.

AI-Powered Analysis

AILast updated: 11/25/2025, 14:21:36 UTC

Technical Analysis

CVE-2025-13347 identifies a SQL injection vulnerability in SourceCodester Train Station Ticketing System version 1.0, specifically in the /ajax.php?action=save_user endpoint. The vulnerability arises from improper sanitization of the Username parameter, allowing attackers to inject malicious SQL code. This flaw can be exploited remotely without requiring authentication or user interaction, making it accessible to a wide range of threat actors. The CVSS 4.0 base score of 5.3 reflects a medium severity, considering the attack vector is network-based with low complexity and no privileges or user interaction needed, but with limited impact on confidentiality, integrity, and availability. Exploitation could lead to unauthorized data access, modification, or deletion within the backend database, potentially compromising user data and operational integrity of the ticketing system. Although no known exploits are currently active in the wild, published exploit code increases the likelihood of future attacks. The vulnerability affects only version 1.0 of the software, and no official patches have been linked yet. The ticketing system is likely deployed in transportation sectors, making it a critical component for operational continuity and customer data protection. The vulnerability underscores the importance of secure coding practices such as input validation and the use of parameterized queries to prevent SQL injection attacks.

Potential Impact

For European organizations, particularly those involved in public transportation and ticketing services, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access to sensitive customer information, including personal and payment data, resulting in privacy violations and regulatory non-compliance under GDPR. Operational disruptions could occur if attackers modify or delete critical ticketing data, potentially causing service outages or financial losses. The reputational damage from a successful attack could undermine public trust in transportation providers. Additionally, attackers could leverage the compromised systems as a foothold for further network intrusion or lateral movement. Given the critical role of train station ticketing systems in European transport infrastructure, the impact extends beyond individual organizations to affect broader public services and mobility. The medium severity rating suggests a moderate but tangible threat that requires timely attention to prevent escalation.

Mitigation Recommendations

Organizations should immediately implement input validation and sanitization on the Username parameter within the /ajax.php?action=save_user endpoint to prevent SQL injection. Employing parameterized queries or prepared statements is essential to eliminate direct injection risks. Network-level mitigations such as web application firewalls (WAFs) can help detect and block malicious payloads targeting this vulnerability. Monitoring and logging of database queries and application logs should be enhanced to identify suspicious activities indicative of exploitation attempts. Since no official patch is currently available, organizations should consider isolating or restricting access to the affected endpoint where feasible. Conducting a thorough security audit of the entire application codebase for similar injection flaws is advisable. Additionally, organizations should prepare incident response plans tailored to potential data breaches or service disruptions stemming from this vulnerability. Regular backups and recovery procedures must be verified to ensure resilience against data tampering or loss.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-11-18T06:53:24.330Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 691c7a583fd37bbc3955e44c

Added to database: 11/18/2025, 1:53:28 PM

Last enriched: 11/25/2025, 2:21:36 PM

Last updated: 1/7/2026, 6:07:28 AM

Views: 62

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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.

Latest Threats