# CVE-2023-51318: Cross-site scripting in n/a

> Attackers can inject malicious scripts via title and name parameters in PHPJabbers Bus Reservation System, potentially compromising user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 20 Feb 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-hq6p-qj55-2rrc

## What is CVE-2023-51318?

CVE-2023-51318 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Feb 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

PHPJabbers Bus Reservation System v1.1 is vulnerable to Multiple Stored Cross-Site Scripting (XSS) in the "title, name" parameters.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-51318?

It affects 1 product.


Products: Phpjabbers Bus Reservation System.

## How do I fix CVE-2023-51318?

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

## Is CVE-2023-51318 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-53877](https://insights.sbomify.com/CVE-2023-53877/): Bus Reservation System 1.1 Multiple SQL Injection via pickup_id Parameter (critical 9.3)
- [CVE-2023-51319](https://insights.sbomify.com/CVE-2023-51319/): Code injection in n/a (high 8.8)
- [CVE-2023-51316](https://insights.sbomify.com/CVE-2023-51316/): Denial of service in n/a (high 7.5)
- [CVE-2023-4111](https://insights.sbomify.com/CVE-2023-4111/): PHP Jabbers Bus Reservation System index.php cross site scripting (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51318 and fix it if it is affected.

What it is: CVE-2023-51318 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Feb 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-2023-51318 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-2023-51318/ (Markdown: https://insights.sbomify.com/CVE-2023-51318/index.md)
```

## Sources

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

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