WordPress Core 2.1.1 - Supply Chain Compromise

2007-03-02 00:00
Anonymous

Strategic Overview

Status
Patched in 2.1.2
Affected Core
WordPress 2.1
Affected Version
2.1.1
CVSS
9.8Critical
Weakness type
CWE-506 · Embedded Malicious Code
CVE
CVE pending
View all WordPress 2.1 vulnerabilities

At a glance

This record tracks a critical-severity Embedded Malicious Code vulnerability in the WordPress 2.1 WordPress release line, affecting 2.1.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.1.2; sites on affected versions should update now. Disclosed March 2007.

Vulnerability Overview

Version 2.1.1 of WordPress was injected with malicious code that supplied attackers with backdoor access to WordPress sites.

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

CWE-506: Embedded Malicious Code

Reaching this weakness in WordPress 2.1 2.1.1 takes a caller who can reach the endpoint. Embedded malicious code means functionality was deliberately placed in the software to act against the site owner's interest, rather than being an accidental defect.

Removing the software is not enough on its own — anything it created or modified while active has to be audited too. For WordPress 2.1 the fix is 2.1.2: builds 2.1.1 are affected, anything from 2.1.2 onward is not.

Remediation

Update to version 2.1.2, or a newer patched version

How does WordSec protect against this?

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: updating to 2.1.2 is the step that ends it.

  • Scanner
  • Alerts

External References

Related records

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