CVE-2007-1244

WordPress Core <= 2.1.1 - Cross-Site Scripting

2007-03-02 00:00

Strategic Overview

Status: Patched in 2.1.2
Affected Core: WordPress 2.1
Affected Version: <= 2.1.1
CVSS: 6.4Medium
Weakness type: CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE: CVE-2007-1244

At a glance

CVE-2007-1244 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WordPress 2.1 WordPress release line, affecting <= 2.1.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.1.2; sites on affected versions should update now. Disclosed March 2007.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the AdminPanel in WordPress 2.1.1 and earlier allows remote attackers to perform privileged actions as administrators, as demonstrated using the delete action in wp-admin/post.php. NOTE: this issue can be leveraged to perform cross-site scripting (XSS) attacks and steal cookies via the post parameter.

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.1 <= 2.1.1 takes a caller who can reach the endpoint. 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.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?

The attempt arrives as an ordinary request to WordPress 2.1: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 2.1.2 is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2007-1244 https://www.wordfence.com/threat-intel/vulnerabilities/id/c6670e56-ae81-4b1b-8274-bf355a411e92 https://nvd.nist.gov/vuln/detail/CVE-2007-1244

Related records

Same weakness class

Other vulnerabilities in WordPress 2.1

CVSS Vector

6.4

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/