WordPress up to 1.2 CSRF Protection wp_create_nonce cross-site request forgery ⚔ [Disputed]

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.7$0-$5k0.00

Summaryinfo

A vulnerability has been found in WordPress up to 1.2 and classified as problematic. This impacts the function wp_create_nonce of the component CSRF protection. The manipulation leads to cross-site request forgery. This vulnerability is uniquely identified as CVE-2012-1936. The attack is possible to be carried out remotely. Moreover, an exploit is present. The presence of this vulnerability remains uncertain at this time. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in WordPress up to 1.2 (Content Management System). This issue affects the function wp_create_nonce of the component CSRF Protection. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

** DISPUTED ** 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.

The weakness was disclosed 05/03/2012 by Ivano Binetti (Website). It is possible to read the advisory at webapp-security.com. The identification of this vulnerability is CVE-2012-1936 since 03/28/2012. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 59048 (WordPress < 3.3.2 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 12598 (WordPress Multiple Cross-Site Request Forgery Vulnerabilities).

Upgrading eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Exploit-DB (18791), Tenable (59048) and SecurityFocus (BID 53280†). The entries VDB-4581, VDB-60055, VDB-60054 and VDB-60053 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 5.7

VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 59048
Nessus Name: WordPress < 3.3.2 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/20/2011 🔍
03/28/2012 +343 days 🔍
04/27/2012 +30 days 🔍
05/03/2012 +6 days 🔍
05/03/2012 +0 days 🔍
05/09/2012 +6 days 🔍
03/23/2015 +1048 days 🔍
01/02/2025 +3573 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: webapp-security.com
Researcher: Ivano Binetti
Status: Confirmed
Disputed: 🔍

CVE: CVE-2012-1936 (🔍)
GCVE (CVE): GCVE-0-2012-1936
GCVE (VulDB): GCVE-100-60707
SecurityFocus: 53280 - WordPress Anti-CSRF Token Security Bypass Weakness

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/23/2015 16:50
Updated: 01/02/2025 13:07
Changes: 03/23/2015 16:50 (53), 02/17/2019 10:35 (14), 06/22/2024 06:08 (16), 08/06/2024 22:39 (1), 01/02/2025 13:07 (5)
Complete: 🔍
Cache ID: 216:46B:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!