dbcve.org
Auto Taxi Stand Management SystemApplication · Phpgurukul

CVE-2025-57145

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A cross-site scripting (XSS) vulnerability exists in the search-autootaxi.php endpoint of the ATSMS web application. The application fails to properly sanitize user input submitted through a form field, allowing an attacker to inject arbitrary JavaScript code. The malicious payload is stored in the backend and executed when a user or administrator accesses the affected report page. This allows attackers to exfiltrate session cookies, hijack user sessions, and perform unauthorized actions in the context of the victims browser.

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 confidence

This is a stored (persistent) cross-site scripting vulnerability in the search-autootaxi.php endpoint of the ATSMS web application. User-supplied input from a form field is not sanitized before being stored in the backend database, and the malicious payload is executed when users or administrators view the affected report page, enabling session hijacking via cookie exfiltration.

MitigationImplement proper input validation and output encoding/sanitization on all user-supplied data in search-autootaxi.php before storage and before rendering on the report page.

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
Auto Taxi Stand Management SystemApplication
Affected:= 1.0

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ATSMS installation and version
    Locate the Auto Taxi Stand Management System installation directory and identify the version number, typically found in a README file, version config, or the main index page footer.
    Affected if The installed version is exactly 1.0 of Phpgurukul Auto Taxi Stand Management System.
  2. Locate the vulnerable endpoint
    Check for the existence of search-autootaxi.php in the web application's root or scripts directory.
    Affected if The file search-autootaxi.php exists in the application.
  3. Identify the report output page
    Examine the application to find the page that displays results or reports from the search-autootaxi.php functionality (typically a report, list, or results page that retrieves stored search data).
    Affected if A report page exists that displays data submitted through search-autootaxi.php.
  4. Check input handling in source code
    Inspect the search-autootaxi.php source code to determine if form input fields are sanitized or validated before being stored in the database.
    Affected if User-supplied input from the search form is stored in the database without sanitization or encoding.
  5. Verify output encoding on report page
    Examine the report page source code that displays stored data from search-autootaxi.php to see if output is encoded or if raw data is rendered.
    Affected if Stored data is rendered on the report page without proper HTML encoding, allowing script execution.

If Phpgurukul Auto Taxi Stand Management System version 1.0 is running with the search-autootaxi.php endpoint and the report page displays unsanitized user input, the environment is affected by this stored XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/sanitization on all user-supplied data in search-autootaxi.php before storage and before rendering on the report page.

Fix this in Auto Taxi Stand Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57145 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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