Approved changes feed: RSS · Atom
cpe:2.3:a:wordpress:wordpress:3.0.3:*:iis:*:*:*:*:*
part: a version: 3.0.3 update: *
| Vendor | Wordpress (21977de4-0364-5ea6-90ad-48069434cf00) |
|---|---|
| Product | Wordpress (56378cf2-4348-590a-a4d7-419fcf17f3f1) |
| Edition | iis |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/wordpress/wordpress |
purl2cpe | 2026-06-01 10:12:03.526820 |
pkg:github/wordpress/wordpress-develop |
purl2cpe | 2026-06-01 10:12:03.526822 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2012-1936 |
vulnerable | 2026-06-08 05:00:51.566698 |
Details available
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
Published: 2012-05-03T20:00:00.000Z
Updated: 2024-08-06T19:17:26.983Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.