# CVE-2014-2021: Cross-site scripting in n/a

> Authenticated attackers can inject arbitrary scripts via XMLRPC API requests in vBulletin, potentially leading to session hijacking or code execution.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6qpm-jgqq-hh7p

## What is CVE-2014-2021?

CVE-2014-2021 is a low-severity cross-site scripting vulnerability in Vbulletin Vbulletin, published on 25 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-site scripting (XSS) vulnerability in admincp/apilog.php in vBulletin 4.2.2 and earlier, and 5.0.x through 5.0.5 allows remote authenticated users to inject arbitrary web script or HTML via a crafted XMLRPC API request, as demonstrated using the client name.

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

## Which versions are affected by CVE-2014-2021?

It affects 1 product.


Products: Vbulletin Vbulletin.

## How do I fix CVE-2014-2021?

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

## Is CVE-2014-2021 being exploited?

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

Public exploit code:

- vBulletin 4.x/5.x - AdminCP/ApiLog via xmlrpc API (Authenticated) Persistent Cross-Site Scripting (exploitdb)

## Other vulnerabilities in Vbulletin Vbulletin

- [CVE-2020-17496](https://insights.sbomify.com/CVE-2020-17496/): vBulletin PHP Module Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16759](https://insights.sbomify.com/CVE-2019-16759/): vBulletin PHP Module Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-48827](https://insights.sbomify.com/CVE-2025-48827/): vBulletin 5.0.0 through 5.7.5 and 6.0.0 through 6.0.3 allows unauthenticated users to invoke protected API controllers' methods when running (critical 10.0)
- [CVE-2023-25135](https://insights.sbomify.com/CVE-2023-25135/): Deserialization in n/a (critical 9.8)
- [CVE-2020-7373](https://insights.sbomify.com/CVE-2020-7373/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2021 and fix it if it is affected.

What it is: CVE-2014-2021 is a low-severity cross-site scripting vulnerability in Vbulletin Vbulletin, published on 25 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2021 in the wild and no public exploit code.

Affected product: Vbulletin Vbulletin. 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-2014-2021/ (Markdown: https://insights.sbomify.com/CVE-2014-2021/index.md)
```

## Sources

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

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