VYPR
Unrated severityNVD Advisory· Published Jan 6, 2012· Updated Apr 29, 2026

CVE-2012-0287

CVE-2012-0287

Description

Cross-site scripting (XSS) vulnerability in wp-comments-post.php in WordPress 3.3.x before 3.3.1, when Internet Explorer is used, allows remote attackers to inject arbitrary web script or HTML via the query string in a POST operation that is not properly handled by the "Duplicate comment detected" feature.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

WordPress 3.3.x before 3.3.1 has a reflected XSS in wp-comments-post.php triggered by a duplicate comment detection error, exploitable via IE.

Vulnerability

The vulnerability is a cross-site scripting (XSS) flaw in WordPress versions 3.3.x prior to 3.3.1, specifically in the wp-comments-post.php file. The issue arises when the "Duplicate comment detected" feature improperly handles the query string during a POST operation when Internet Explorer is used as the browser. The unescaped query string is reflected in the error page, allowing injection of arbitrary HTML and JavaScript [1][2].

Exploitation

An attacker must first post a legitimate comment to a target WordPress site. Then, they craft a malicious HTML page that posts a comment with the same author, email, and comment values as the previous comment, along with the correct comment_post_ID. The form's action URL includes a query string containing the XSS payload: ``. When the victim (using Internet Explorer) submits this form, the server detects a duplicate comment and returns a 500 error page that reflects the payload from the query string, executing the script [1].

Impact

A successful exploit allows the attacker to execute arbitrary JavaScript or HTML in the victim's browser within the context of the vulnerable WordPress site. This can lead to session hijacking, defacement, or theft of sensitive information. The attack requires the victim to use Internet Explorer and to interact with the attacker-controlled form [1].

Mitigation

WordPress 3.3.1, released on January 3, 2012, fixes this vulnerability along with other issues. Users should upgrade to version 3.3.1 or later. No workaround is available if the site cannot be upgraded. This CVE is not listed on the CISA KEV [2].

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

4

News mentions

0

No linked articles in our index yet.