CVE-2021-24823

Support Board < 3.3.6 - Cross-Site Request Forgery

Strategic Overview

Status
Patched in 3.3.6
Affected Plugin
Support Board
Affected Version
< 3.3.6
CVSS
8.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-24823
View all Support Board vulnerabilities

At a glance

CVE-2021-24823 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Support Board WordPress plugin, affecting versions < 3.3.6. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.3.6; sites on affected versions should update now. Disclosed October 2021, reported by Brandon James Roldan (tomorrowisnew).

Vulnerability Overview

The Support Board WordPress plugin before 3.3.6 does not have any CSRF checks in actions handled by the include/ajax.php file, which could allow attackers to make logged in users do unwanted actions. For example, make an admin delete arbitrary files

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on integrity, availability.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Support Board < 3.3.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Support Board the fix is 3.3.6: builds < 3.3.6 are affected, anything from 3.3.6 onward is not.

Remediation

Update to version 3.3.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Support Board: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Support Board 3.3.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C