CVE-2012-6692

Yoast SEO <= 2.1.1 - Cross Site Scripting via post_title parameter

2012-10-31 00:00
Anonymous

Strategic Overview

Status
Patched in 2.2
Affected Plugin
Yoast SEO – Advanced SEO with real-time guidance and built-in AI
Affected Version
<= 2.1.1
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2012-6692
View all Yoast SEO – Advanced SEO with real-time guidance and built-in AI vulnerabilities

At a glance

CVE-2012-6692 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Yoast SEO WordPress plugin, affecting versions <= 2.1.1. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2; sites on affected versions should update now. Disclosed October 2012.

Vulnerability Overview

Cross-site scripting (XSS) vulnerability in js/wp-seo-metabox.js in the WordPress SEO by Yoast plugin before 2.2 for WordPress allows remote attackers to inject arbitrary web script or HTML via the post_title parameter to wp-admin/post-new.php, which is not properly handled in the snippet preview functionality.

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.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Yoast SEO <= 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 Yoast SEO the fix is 2.2: builds <= 2.1.1 are affected, anything from 2.2 onward is not.

Remediation

Update to version 2.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Yoast SEO: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Yoast SEO 2.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2012-6692https://www.wordfence.com/threat-intel/vulnerabilities/id/4187f559-87ba-46ab-9b45-7a36dd98d71dhttps://nvd.nist.gov/vuln/detail/CVE-2012-6692

Related records

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