CVE-2021-24226

AccessAlly <= 3.5.6 - Information Exposure

2021-03-26 00:00
Till Krüss

Strategic Overview

Status
Patched in 3.5.7
Affected Plugin
AccessAlly
Affected Version
<= 3.5.6
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2021-24226
View all AccessAlly vulnerabilities

At a glance

CVE-2021-24226 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the AccessAlly WordPress plugin, affecting versions <= 3.5.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.5.7; sites on affected versions should update now. Disclosed March 2021, reported by Till Krüss.

Vulnerability Overview

In the AccessAlly WordPress plugin before 3.5.7, the file "resource/frontend/product/product-shortcode.php" responsible for the [accessally_order_form] shortcode is dumping serialize($_SERVER), which contains all environment variables. The leakage occurs on all public facing pages containing the [accessally_order_form] shortcode, no login or administrator role is required.

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, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in AccessAlly <= 3.5.6 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For AccessAlly the fix is 3.5.7: builds <= 3.5.6 are affected, anything from 3.5.7 onward is not.

Remediation

Update to version 3.5.7, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: AccessAlly 3.5.7 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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