Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2016-6483: SSRF in vBulletin Media-File Upload Feature

Published Sep 2, 2016 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v3
EPSS12.9%96th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Vbulletin
IdentifiersCVE-2016-6483CWE-918 · Server-Side Request Forgery (SSRF)

A server-side request forgery (SSRF) vulnerability exists in the media-file upload feature of vBulletin versions prior to 3.8.7 Patch Level 6, 3.8.8 Patch Level 2, 3.8.9 Patch Level 1, 4.2.2 Patch Level 6, 4.2.3 Patch Level 2, 5.2.0 Patch Level 3, 5.2.1 Patch Level 1, and 5.2.2 Patch Level 1. The vulnerability allows remote attackers to supply a crafted URL that triggers an HTTP redirection, enabling the attacker to make the server perform arbitrary HTTP requests to internal or external resources.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to leverage the vBulletin server to make arbitrary HTTP requests, potentially accessing internal network resources, bypassing firewall restrictions, or interacting with services not intended to be exposed externally. This can lead to information disclosure, further attacks on internal infrastructure, or abuse of trust relationships.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict outbound HTTP requests from the vBulletin server at the network level, and validate or sanitize user-supplied URLs in the media-file upload feature to prevent redirection to arbitrary destinations.

Remediation

Patch, then assume compromise.

Upgrade vBulletin to at least 3.8.7 Patch Level 6, 3.8.8 Patch Level 2, 3.8.9 Patch Level 1, 4.2.2 Patch Level 6, 4.2.3 Patch Level 2, 5.2.0 Patch Level 3, 5.2.1 Patch Level 1, or 5.2.2 Patch Level 1, depending on your version branch. These versions contain patches that address the SSRF vulnerability in the media-file upload feature.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
VbulletinVbulletinapplication
FAQ

Frequently asked questions

Is CVE-2016-6483 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2016-6483 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2016-6483?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2016-6483.
Is there a patch for CVE-2016-6483?
Upgrade vBulletin to at least 3.8.7 Patch Level 6, 3.8.8 Patch Level 2, 3.8.9 Patch Level 1, 4.2.2 Patch Level 6, 4.2.3 Patch Level 2, 5.2.0 Patch Level 3, 5.2.1 Patch Level 1, or 5.2.2 Patch Level 1, depending on your version branch. These versions contain patches that address the SSRF vulnerability in the media-file upload feature.
What products are affected by CVE-2016-6483?
Vbulletin.
How severe is CVE-2016-6483?
CVE-2016-6483 has a CVSS v3 score of 8.6 (High) and an EPSS score of 12.9% (96th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.