Auto Prune Posts
Approved changes feed: RSS · Atom
cpe:2.3:a:klarned:auto_prune_posts:*:*:*:*:*:wordpress:*:*part: a version: * update: *
| Vendor | Klarned (08f19512-be76-54a8-bf22-47b2a0b493ac) |
|---|---|
| Product | Auto Prune Posts (f1b9f770-b59e-5ba1-a7f7-72a8d8c07916) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/common-repository/auto-prune-posts |
purl2cpe | 2026-07-28 16:41:16.819116 |
pkg:github/wp-plugins/auto-prune-posts |
purl2cpe | 2026-06-01 10:17:59.967524 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-10639 |
vulnerable | 2026-06-08 06:23:47.154526 |
Auto Prune Posts < 3.0.0- Admin+ Stored XSS
The Auto Prune Posts WordPress plugin before 3.0.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
Published: 2025-05-15T20:06:45.594Z
Updated: 2025-05-20T19:37:25.707Z |
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.