Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2020-17496: Pre-auth RCE in vBulletin widget_tabbedcontainer_tab_panel

Published Aug 12, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS87.5%100th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Vbulletin
IdentifiersCVE-2020-17496CWE-78

CVE-2020-17496 is a pre-authentication remote command execution vulnerability in vBulletin affecting versions 5.5.4 through 5.6.2. The flaw is a bypass of the earlier fix for CVE-2019-16759 and arises from incomplete hardening of vBulletin’s template rendering logic for Ajax requests. An attacker can send a crafted ajax/render/widget_tabbedcontainer_tab_panel request containing malicious subWidgets data that causes the application to load a child widget template in an unsafe way. By assigning the PHP-capable widget template as a child template and supplying attacker-controlled code through widget configuration data, the request reaches the PHP evaluation path used by vBulletin’s template runtime, resulting in execution of attacker-supplied commands on the server. The issue is remotely reachable without prior authentication and has been observed exploited in the wild.

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 an unauthenticated remote attacker to execute arbitrary commands in the security context of the web application on the underlying vBulletin server. This can enable full site compromise, deployment of web shells or other malware, reading of sensitive server-side files, modification of application content or configuration, use of the host for follow-on attacks, and potentially broader compromise depending on the privileges of the web server process and local environment.

Mitigation

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

If immediate patching is not possible, reduce exposure by restricting public access to the vulnerable Ajax rendering endpoint, placing the forum behind a reverse proxy or access-control layer, and using WAF rules to block suspicious requests targeting widget rendering with attacker-controlled subWidgets data. Disable or tightly limit unnecessary template rendering functionality where operationally feasible. Monitor application and web server logs for anomalous requests to Ajax widget-rendering routes and investigate for post-exploitation artifacts. These measures are temporary and do not replace vendor patching.

Remediation

Patch, then assume compromise.

Upgrade vBulletin to a vendor-fixed release that fully addresses CVE-2020-17496. Because the issue is explicitly caused by an incomplete fix for CVE-2019-16759, organizations should ensure they are not relying on the earlier partial remediation alone and should apply the later security patch released for affected 5.6.x versions. After patching, review the server for signs of compromise, including unauthorized code execution, web shell placement, malicious file changes, and secondary payload deployment, because exploitation was observed in the wild.

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-2020-17496 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2020-17496?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2020-17496, the earliest disclosed Aug 9, 2020.
Is there a patch for CVE-2020-17496?
Upgrade vBulletin to a vendor-fixed release that fully addresses CVE-2020-17496. Because the issue is explicitly caused by an incomplete fix for CVE-2019-16759, organizations should ensure they are not relying on the earlier partial remediation alone and should apply the later security patch released for affected 5.6.x versions.
What products are affected by CVE-2020-17496?
Vbulletin.
How severe is CVE-2020-17496?
CVE-2020-17496 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 87.5% (100th percentile) as of Oct 16, 2026.
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 malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, 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.