# CVE-2019-16759: vBulletin PHP Module Remote Code Execution

> Remote attackers can execute arbitrary code on vBulletin servers by injecting PHP code into the widget configuration parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-c7wq-5768-48mp

## What is CVE-2019-16759?

CVE-2019-16759 is a critical code injection vulnerability in Vbulletin Vbulletin, published on 24 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

vBulletin 5.x through 5.5.4 allows remote command execution via the widgetConfig[code] parameter in an ajax/render/widget_php routestring request.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2019-16759?

It affects 1 product.


Products: Vbulletin Vbulletin.

## How do I fix CVE-2019-16759?

No fix has been published for CVE-2019-16759 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-16759 being exploited?

Yes. Attackers have exploited CVE-2019-16759 in the wild since at least 3 Nov 2021.

Public exploit code:

- vBulletin 5.x  未授权远程代码执行漏洞 (github_poc): https://github.com/jas502n/CVE-2019-16759
- CVE-2019-16759 vbulletin 5.0.0 till 5.5.4 pre-auth rce (github_poc): https://github.com/theLSA/vbulletin5-rce
- This tools will extracts and dumps Email + SMTP from vBulletin database server (github_poc): https://github.com/0xdims/CVE-2019-16759
- Vbulletin rce exploit CVE-2019-16759 (github_poc): https://github.com/M0sterHxck/CVE-2019-16759-Vbulletin-rce-exploit
- Interactive-Like Command-Line Console for CVE-2019-16759 (github_poc): https://github.com/FarjaalAhmad/CVE-2019-16759
- Identify vulnerable (RCE) vBulletin 5.0.0 - 5.5.4 instances using Shodan (CVE-2019-16759) (github_poc): https://github.com/andripwn/pwn-vbulletin

## 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-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)
- [CVE-2020-12720](https://insights.sbomify.com/CVE-2020-12720/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16759 and fix it if it is affected.

What it is: CVE-2019-16759 is a critical code injection vulnerability in Vbulletin Vbulletin, published on 24 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-16759 in the wild since at least 3 Nov 2021.

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

## Sources

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

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