# CVE-2018-14575: Cross-site scripting in n/a

> Attackers can execute scripts or perform actions via XSS and CSRF in the MyBB Trash Bin plugin, potentially compromising user accounts.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-63j4-jx57-q5fw

## What is CVE-2018-14575?

CVE-2018-14575 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Trash Bin plugin 1.1.3 for MyBB has cross-site scripting (XSS) via a thread subject and a cross-site request forgery (CSRF) via a post subject.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-14575?

It affects 1 product.


Products: Mybb Trash Bin.

## How do I fix CVE-2018-14575?

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

## Is CVE-2018-14575 being exploited?

There is no known exploitation of CVE-2018-14575 in the wild and no public exploit code.

Public exploit code:

- MyBB Trash Bin Plugin 1.1.3 - Cross-Site Scripting / Cross-Site Request Forgery (exploitdb)
- MyBB Trash Bin Plugin 1.1.3 - Cross-Site Scripting / Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14575 and fix it if it is affected.

What it is: CVE-2018-14575 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-14575 in the wild and no public exploit code.

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-2018-14575/ (Markdown: https://insights.sbomify.com/CVE-2018-14575/index.md)
```

## Sources

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

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