CVE-2012-10025

Advanced Custom Fields <= 3.5.1 - Remote Code Execution via Remote File Inclusion

2013-01-03 00:00
Anonymous

Strategic Overview

Status
Patched in 3.5.2
Affected Plugin
Advanced Custom Fields (ACF®)
Affected Version
<= 3.5.1
CVSS
3.8Low
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2012-10025
View all Advanced Custom Fields (ACF®) vulnerabilities

At a glance

CVE-2012-10025 is a low-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Advanced Custom Fields (ACF®) WordPress plugin, affecting versions <= 3.5.1. It carries a CVSS score of 3.8 (reachable over the network; low attack complexity). The issue is fixed in version 3.5.2; sites on affected versions should update now. Disclosed January 2013.

Vulnerability Overview

Advanced Custom Fields up to 3.5.1 is vulnerable to Remote Code Execution. The vulnerability allows for remote file inclusion and remote code execution via the export.php script. This exploit only works when the php option allow_url_include is set to On (Default Off).

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-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Reaching this weakness in Advanced Custom Fields (ACF®) <= 3.5.1 takes a caller who can reach the endpoint. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For Advanced Custom Fields (ACF®) the fix is 3.5.2: builds <= 3.5.1 are affected, anything from 3.5.2 onward is not.

Remediation

Update to version 3.5.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Advanced Custom Fields (ACF®): WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Advanced Custom Fields (ACF®) 3.5.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2012-10025https://www.wordfence.com/threat-intel/vulnerabilities/id/3dfba044-42f8-44a2-be62-99af9d9094c3https://nvd.nist.gov/vuln/detail/CVE-2012-10025

Related records

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