404 To 301
Approved changes feed: RSS · Atom
cpe:2.3:a:404_to_301_project:404_to_301:*:*:*:*:*:wordpress:*:*
part: a version: * update: *
| Vendor | 404 To 301 Project (928d7959-ea57-55fa-b055-8958b32fd810) |
|---|---|
| Product | 404 To 301 (109b78e1-8882-5d57-94b6-823de914ecbf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/joel-james/404-to-301 |
purl2cpe | 2026-06-01 10:16:30.105488 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-24766 |
vulnerable | 2026-06-08 05:30:39.196293 |
404 to 301 < 3.0.9 - Logs Deletion via CSRF
The 404 to 301 – Redirect, Log and Notify 404 Errors WordPress plugin before 3.0.9 does not have CSRF check in place when cleaning the logs, which could allow attacker to make a logged in admin delete all of them via a CSRF attack
Published: 2021-11-08T17:35:17.000Z
Updated: 2024-08-03T19:42:16.949Z |
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.