# CVE-2016-6483: Server-side request forgery in n/a

> Remote attackers can exploit a media upload flaw in vBulletin to perform Server-Side Request Forgery attacks via crafted URLs.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-54rx-pqvg-4w6x

## What is CVE-2016-6483?

CVE-2016-6483 is a high-severity server-side request forgery vulnerability in Vbulletin Vbulletin, published on 2 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The media-file upload feature in vBulletin before 3.8.7 Patch Level 6, 3.8.8 before Patch Level 2, 3.8.9 before Patch Level 1, 4.x before 4.2.2 Patch Level 6, 4.2.3 before Patch Level 2, 5.x before 5.2.0 Patch Level 3, 5.2.1 before Patch Level 1, and 5.2.2 before Patch Level 1 allows remote attackers to conduct SSRF attacks via a crafted URL that results in a Redirection HTTP status code.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2016-6483?

It affects 1 product.


Products: Vbulletin Vbulletin.

## How do I fix CVE-2016-6483?

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

## Is CVE-2016-6483 being exploited?

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

Public exploit code:

- vBulletin 5.2.2 - Server-Side Request Forgery (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-2016-6483 and fix it if it is affected.

What it is: CVE-2016-6483 is a high-severity server-side request forgery vulnerability in Vbulletin Vbulletin, published on 2 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6483 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-2016-6483/ (Markdown: https://insights.sbomify.com/CVE-2016-6483/index.md)
```

## Sources

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

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