CVE-2025-13344
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA weakness has been identified in SourceCodester Train Station Ticketing System 1.0. Affected by this vulnerability is an unknown functionality of the file /ajax.php?action=login. This manipulation of the argument Username causes sql injection. The attack can be initiated remotely. The exploit has been made available to the public and could be exploited.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the login functionality of SourceCodester Train Station Ticketing System 1.0. The Username parameter in /ajax.php?action=login is not properly sanitized, allowing attackers to inject malicious SQL queries remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of the Train Station Ticketing SystemLocate the application files and check for version identifiers in source files, README, or configuration files. Look for version numbers in the application root directory or within PHP files that contain version comments.Affected if The installed version is 1.0 (Oretnom23 Train Station Ticketing System)
-
Locate the vulnerable ajax.php fileSearch for the file ajax.php in the web application root directory. This file typically handles AJAX requests including the login action.Affected if The file /ajax.php exists and is accessible via the web server
-
Examine the login function in ajax.phpOpen ajax.php and locate the code handling the 'login' action. Look for the section that processes the Username parameter from POST or GET requests.Affected if The login action handler processes the Username parameter without proper input handling
-
Check for lack of parameterized queries in the login SQL queryReview the SQL query used in the login function. Inspect whether user input (Username) is concatenated directly into the SQL string or passed as a parameter to a prepared statement.Affected if The Username parameter is concatenated directly into the SQL query string rather than being bound as a parameter to a prepared statement
-
Verify the login endpoint is accessibleAttempt to access or analyze the /ajax.php?action=login endpoint. This can be done via web request testing or by confirming the route exists in the application routing logic.Affected if The login endpoint is publicly or internally accessible and accepts user input for the Username field
The environment is affected if the Train Station Ticketing System version 1.0 is installed and the ajax.php login function uses direct string concatenation for the Username parameter instead of parameterized queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries or prepared statements. Implement proper input validation and escaping for all user-supplied data before using it in SQL queries.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13344 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data