CVE-2022-2594

Advanced Custom Fields <= 5.12.2 - File Upload

2022-07-14 00:00
James Golovich

Strategic Overview

Status
Patched in 5.12.3
Affected Plugin
Advanced Custom Fields (ACF®)
Affected Version
<= 5.12.2
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-2594
View all Advanced Custom Fields (ACF®) vulnerabilities

At a glance

CVE-2022-2594 is a medium-severity Missing Authorization vulnerability in the Advanced Custom Fields (ACF®) WordPress plugin, affecting versions <= 5.12.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 5.12.3; sites on affected versions should update now. Disclosed July 2022, reported by James Golovich.

Vulnerability Overview

The Advanced Custom Fields plugin for WordPress has a file upload vulnerability in versions up to, and including, 5.12.2. This allows users without the upload_files capability, such as contributors, or unauthenticated users in cases where a frontend form is added to the site, to upload allowed file types. The upload is handled by WordPress so file type and extension checks still occur, though this could potentially be used by high-privileged users in certain locked-down configurations to bypass other security mechanisms and upload dangerous file types.

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

CWE-862: Missing Authorization

Reaching this weakness in Advanced Custom Fields (ACF®) <= 5.12.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Advanced Custom Fields (ACF®) the fix is 5.12.3: builds <= 5.12.2 are affected, anything from 5.12.3 onward is not.

Remediation

Update to version 5.12.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Advanced Custom Fields (ACF®) 5.12.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-2594https://www.wordfence.com/threat-intel/vulnerabilities/id/e5bab390-1590-44f2-8c65-bc329955ed84https://nvd.nist.gov/vuln/detail/CVE-2022-2594

Related records

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