CriticalCVE-2020-17496

    vBulletin PHP Module Remote Code Execution Vulnerability (CVE-2020-17496)

    Published In CISA KEV since Sources: CVE.org

    Share

    What is affected, what to do

    A vulnerability in vBulletin allows remote code execution (RCE) via manipulated subWidgets data in an ajax/render/widget_tabbedcontainer_tab_panel request. An attacker can gain full control of the instance without authentication. The vulnerability is listed in the CISA KEV catalog and actively exploited in ransomware campaigns. Affected products are vBulletin versions 5.5.4 to 5.6.2. A patch is urgently needed to address this security issue.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • vBulletin lte 5.5.4..5.6.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org

    87.5 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.76

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    228.62 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    87.5 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.76
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 4 February 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-74

    Response and mitigation

    Why act now?

    Prioritisation rationale

    A one-line public exploit for this bug has existed since 2020 and was baked into mass-scanning toolkits almost immediately; the KEV listing confirms sustained in-the-wild use. Typical attacker goals are webshell drop, cryptomining and using the host as a pivot into shared hosting or SSO back-ends, so any internet-reachable vBulletin instance in the 5.5.4–5.6.2 range should be treated as presumptively compromised, not merely exposed. Rate this a P1 incident with a full compromise assessment if such an instance exists in your perimeter; even internal forums deserve a 24-hour patch window because an unauthenticated RCE on a federated identity consumer can escalate quickly. The combination of very high exploitation likelihood and an unauthenticated network attack surface means compensating controls alone are not an acceptable long-term stance.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Upgrade vBulletin to a fixed release (5.6.3 or later per vendor advisory) immediately. CVE-2020-17496 is the bypass of an incomplete fix for CVE-2019-16759, so pre-5.6.3 hotfixes are not sufficient.
      • If a full upgrade is blocked, apply the vendor hotfix that neutralises widget_tabbedcontainer_tab_panel rendering (template edit / $config['Misc']['rendertype'] workaround as published by vBulletin).
      • Place the forum behind a WAF or set it to maintenance mode until patched, especially for internet-facing instances on port 80/443.
      • Compromise check: scan the webroot (/forum, /community) for new or modified PHP files (webshells) created since July 2020; review access logs for any request to ajax/render/widget_tabbedcontainer_tab_panel.
      • Review PHP process privileges. If the web server (www-data, apache) can write into the webroot, remount read-only and rotate admin passwords, DB credentials and API keys.

    2. Runbook step 2

      Mitigation layers

      • Network: restrict /admincp/ and /modcp/ to admin source IPs or VPN at the reverse proxy; apply an egress allowlist on the web server to kill reverse shells and tool staging.
      • WAF/IPS: block POST and GET requests to ajax/render/widget_tabbedcontainer_tab_panel carrying subWidgets[ or widgetConfig[code]. Enable ModSecurity / Snort / Suricata signatures covering CVE-2019-16759 and CVE-2020-17496 (Emerging Threats and Snort Community have both).
      • Endpoint hardening: extend PHP disable_functions to include exec, passthru, shell_exec, system, popen, proc_open, pcntl_exec; set open_basedir; mount webroot read-only.
      • IAM / least privilege: dedicated DB user for vBulletin without FILE/SUPER privileges; enforce MFA on the admin panel; set session cookies to HttpOnly, Secure, SameSite=Strict.
      • Configuration: disable the widget_tabbedcontainer_tab_panel widget if the forum does not functionally require it; disable template editing in AdminCP; validate template caches against a known-good baseline.
      • Monitoring: forward all web access logs to the SIEM with at least 90-day retention to allow retrospective incident reconstruction.

    3. Runbook step 3

      Detection rules

      • Access-log pattern (nginx/Apache): POST /ajax/render/widget_tabbedcontainer_tab_panel combined with subWidgets or widgetConfig in the body. Splunk example: index=web uri_path="*widget_tabbedcontainer_tab_panel*" (form_data="*subWidgets*" OR form_data="*widgetConfig*").
      • Sigma shape: selection: cs-uri-stem|contains: 'widget_tabbedcontainer_tab_panel'; cs-method: 'POST'; c-ip|not in internal_admin_ranges — tag matches with MITRE T1190 (Exploit Public-Facing Application).
      • Process ancestry (Sysmon EID 1 / auditd execve): web server process (php-fpm, httpd, apache2, w3wp.exe) spawning sh, bash, wget, curl, python, perl, nc — a reliable post-exploitation marker. KQL: DeviceProcessEvents | where InitiatingProcessFileName in ("php-fpm","httpd","apache2","w3wp.exe") and FileName in ("sh","bash","curl","wget","python","perl","nc").
      • File-system telemetry (Sysmon EID 11 / auditd watch): new .php files under the forum webroot or modifications to core files outside deployment windows.
      • Network telemetry (Zeek/Suricata): egress from the web server to TOR exit nodes, paste sites or freshly observed cloud IPs within seconds of an HTTP POST to the vulnerable endpoint — strong correlation signal for successful RCE.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    vBulletin 5.5.4 through 5.6.2 allows remote command execution via crafted subWidgets data in an ajax/render/widget_tabbedcontainer_tab_panel request. NOTE: this issue exists because of an incomplete fix for CVE-2019-16759.

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    vbulletinvbulletin
    • 5.5.4 – ≤ 5.6.2
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

      Class

      The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

      Entry at MITRE CWE-74

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    Reference tagged as exploitseclists.org (opens in a new tab)PoC (publicly reported)reported, not verified—

    References & sources

    • cwe.mitre.orgdata/definitions/78.htmlx_refsource_MISC, Technical description
    • blog.exploitee.rs2020/exploiting-vbulletin-a-tale-of-patch-failx_refsource_MISC, Exploit, Third-party advisory
    • forum.vbulletin.comforum/vbulletin-announcements/vbulletin-announcements_aa/444522…x_refsource_MISC, Patch, Vendor advisory
    • seclists.orgfulldisclosure/2020/Aug/5x_refsource_MISC, Exploit, Mailing list, Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2020-17496government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2020-17496
    <a href="https://intel.neosec.eu/en/cve/CVE-2020-17496"><img src="https://intel.neosec.eu/badge/cve/CVE-2020-17496.svg?lang=en" alt="CVE-2020-17496 – NEOSEC Intel" height="20"></a>