CVE-2019-15324

Ad Inserter <= 2.4.21 - Authenticated Remote Code Execution

2019-07-15 00:00
Sean Murphy

Strategic Overview

Status
Patched in 2.4.22
Affected Version
<= 2.4.21
CVSS
8.8High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2019-15324
View all Ad Inserter – Ad Manager & AdSense Ads vulnerabilities

At a glance

CVE-2019-15324 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Ad Inserter WordPress plugin, affecting versions <= 2.4.21. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 2.4.22; sites on affected versions should update now. Disclosed July 2019, reported by Sean Murphy.

Vulnerability Overview

The ad-inserter plugin before 2.4.22 for WordPress has remote code execution.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Ad Inserter <= 2.4.21 takes any authenticated account. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Ad Inserter the fix is 2.4.22: builds <= 2.4.21 are affected, anything from 2.4.22 onward is not.

Remediation

Update to version 2.4.22, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Ad Inserter: 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: Ad Inserter 2.4.22 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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