Wordfence 7.2.3 for WordPress
Approved changes feed: RSS · Atom
cpe:2.3:a:wordfence:wordfence:7.2.3:*:*:*:*:wordpress:*:*part: a version: 7.2.3 update: *
| Vendor | Wordfence (4c912c18-d544-562d-ada9-0d92cc13e245) |
|---|---|
| Product | Wordfence (df4f8b53-1fd2-5e87-975f-7bebf37b02ce) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/wp-plugins-mirror/wordfence |
purl2cpe | 2026-06-01 10:11:42.534691 |
pkg:github/wp-plugins/wordfence |
purl2cpe | 2026-06-01 10:11:42.534694 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-9669 |
vulnerable | 2026-06-08 05:14:25.958075 |
Details available
The Wordfence plugin 7.2.3 for WordPress allows XSS via a unique attack vector. NOTE: It has been asserted that this is not a valid vulnerability in the context of the Wordfence WordPress plugin as the firewall rules are not maintained as part of the Wordfence software but rather it is a set of rules hosted on vendor servers and pushed to the plugin with no versioning associated. Bypassing a WAF rule doesn't make a WordPress site vulnerable (speaking in terms of software vulnerabilities)
Published: 2019-04-25T18:18:04.000Z
Updated: 2024-08-04T21:54:45.512Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.