# CVE-2025-57642: File upload in n/a

> Attackers can upload and execute arbitrary PHP scripts in Tourism Management System, leading to remote code execution and data compromise.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-j59x-hwc3-59qp

## What is CVE-2025-57642?

CVE-2025-57642 is a high-severity vulnerability in n/a, published on 10 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A Shell Upload vulnerability in Tourism Management System 2.0 allows an attacker to upload and execute arbitrary PHP shell scripts on the server, leading to remote code execution and unauthorized access to the system. This can result in the compromise of sensitive data and system functionality.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-57642?

It affects 1 product.


Products: Sohamjuhin Tourism Management System.

## How do I fix CVE-2025-57642?

No fix has been published for CVE-2025-57642 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-57642 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57642 exists.

Public exploit code:

- Tourism Management System 2.0 - Arbitrary Shell Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57642 and fix it if it is affected.

What it is: CVE-2025-57642 is a high-severity vulnerability in n/a, published on 10 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57642 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-57642/ (Markdown: https://insights.sbomify.com/CVE-2025-57642/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57642
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57642
- OSV: https://osv.dev/vulnerability/CVE-2025-57642

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-57642/
Summaries are generated and may contain mistakes; the official description above is the record.