CVE-2007-4153

WordPress Core <= 2.2.1 - Authenticated (Admin+) Cross-Site Scripting

2007-08-05 00:00
Anonymous

Strategic Overview

Status
Patched in 2.2.2
Affected Core
WordPress 2.2
Affected Version
<= 2.2.1
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2007-4153
View all WordPress 2.2 vulnerabilities

At a glance

CVE-2007-4153 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WordPress 2.2 WordPress release line, affecting <= 2.2.1. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 2.2.2; sites on affected versions should update now. Disclosed August 2007.

Vulnerability Overview

Multiple cross-site scripting (XSS) vulnerabilities in WordPress 2.2.1 allow remote authenticated administrators to inject arbitrary web script or HTML via (1) the Options Database Table in the Admin Panel, accessed through options.php; or (2) the opml_url parameter to link-import.php. NOTE: this might not cross privilege boundaries in some configurations, since the Administrator role has the unfiltered_html capability.

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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WordPress 2.2 <= 2.2.1 takes an account at Admin level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WordPress 2.2 the fix is 2.2.2: builds <= 2.2.1 are affected, anything from 2.2.2 onward is not.

Remediation

Update to version 2.2.2, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 2.2.2 is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2007-4153https://www.wordfence.com/threat-intel/vulnerabilities/id/8f896e4a-565a-4545-9683-045cd08ccca0https://nvd.nist.gov/vuln/detail/CVE-2007-4153

Related records

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