# CVE-2025-7840: Campcodes Online Movie Theater Seat Reservation System Reserve Your Seat Page index.php cross site scripting

> Attackers can inject malicious scripts via Firstname/Lastname fields in the reservation page, potentially compromising user sessions.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-jj5h-f25w-8hv6

## What is CVE-2025-7840?

CVE-2025-7840 is a medium-severity cross-site scripting vulnerability in Campcodes Online Movie Theater Seat Reservation System, published on 19 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in Campcodes Online Movie Theater Seat Reservation System 1.0. It has been classified as problematic. This affects an unknown part of the file /index.php?page=reserve of the component Reserve Your Seat Page. The manipulation of the argument Firstname/Lastname leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Campcodes Online Movie Theater Seat Reservation System.

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

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

## Is CVE-2025-7840 being exploited?

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

Public exploit code:

- Proof‑of‑concept exploit for CVE‑2025‑7840 that injects malicious payloads into the Firstname parameter of a reservation form to trigger XSS (github_poc): https://github.com/byteReaper77/CVE-2025-7840

## Other vulnerabilities in Campcodes Online Movie Theater Seat Reservation System

- [CVE-2025-7838](https://insights.sbomify.com/CVE-2025-7838/): Campcodes Online Movie Theater Seat Reservation System manage_seat.php sql injection (medium 6.9)
- [CVE-2025-7547](https://insights.sbomify.com/CVE-2025-7547/): Campcodes Online Movie Theater Seat Reservation System admin_class.php save_movie unrestricted upload (medium 6.9)
- [CVE-2025-7454](https://insights.sbomify.com/CVE-2025-7454/): Campcodes Online Movie Theater Seat Reservation System manage_theater.php sql injection (medium 6.9)
- [CVE-2025-7455](https://insights.sbomify.com/CVE-2025-7455/): Campcodes Online Movie Theater Seat Reservation System manage_reserve.php sql injection (medium 6.9)
- [CVE-2025-7456](https://insights.sbomify.com/CVE-2025-7456/): Campcodes Online Movie Theater Seat Reservation System reserve.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7840 is a medium-severity cross-site scripting vulnerability in Campcodes Online Movie Theater Seat Reservation System, published on 19 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7840 exists.

Affected product: Campcodes Online Movie Theater Seat Reservation System. 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-7840/ (Markdown: https://insights.sbomify.com/CVE-2025-7840/index.md)
```

## Sources

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

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