CVE-2012-1936: n/a vulnerability

CVE-2012-1936: The wp_create_nonce function in wp-includes/pluggable.php in WordPress 3.3.1 and earlier associates a nonce...

The wp_create_nonce function in wp-includes/pluggable.php in WordPress 3.3.1 and earlier associates a nonce with a user account instead of a user session, which might make it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks on specific actions and objects by sniffing the network, as demonstrated by attacks against the wp-admin/admin-ajax.php and wp-admin/user-new.php scripts. NOTE: the vendor reportedly disputes the significance of this issue because wp_create_nonce operates as intended, even if it is arguably inconsistent with certain CSRF protection details advocated by external organizations

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 19:17 UTC (UTC+00:00)

Security readout for executives and security teams

This issue concerns very old WordPress sites, version 3.3.1 and earlier. WordPress nonces were tied to the user account rather than a browser session, which could make some CSRF attacks easier if an attacker obtained a valid nonce. The vendor reportedly disputed the significance of the finding. Exposure is mainly legacy WordPress 3.3.1 and earlier installations, especially admin workflows conducted over networks where nonce leakage is plausible. Modern or fully maintained WordPress deployments are not identified as affected in the supplied sources. Treat this as a legacy-platform risk rather than an emergency internet-wide crisis. Prioritize finding and removing old WordPress 3.3.1-or-earlier systems, because unsupported CMS software usually carries broader risk than this single disputed nonce issue. Mitigation focus: Inventory WordPress installations and identify any running version 3.3.1 or earlier.; Check WordPress vendor guidance before relying on any CVE-specific fix claim.; Upgrade unsupported WordPress instances to a currently supported release..

Prepared: Jun 24, 2026, 12:52 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2012-1936 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: May 3, 2012, 20:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.