WordPress plugin
Auto Prune Posts security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 3 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High0
- Medium3
- Low0
All Auto Prune Posts vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Cross-Site Request Forgery ≤3.0.0Update to 3.1.0 | CVE-2025-64262 | |
| Medium4.4 | Authenticated (Admin+) Stored Cross-Site Scripting ≤2.0.0Update to 3.0.0 | CVE-2024-10639 | |
| Medium5.4 | Cross-Site Request Forgery via admin_menu ≤1.8.0Update to 2.0.0 | CVE-2023-27423 |
- Medium4.3Cross-Site Request Forgery
≤3.0.0Update to 3.1.0
- Medium4.4Authenticated (Admin+) Stored Cross-Site Scripting
≤2.0.0Update to 3.0.0
- Medium5.4Cross-Site Request Forgery via admin_menu
≤1.8.0Update to 2.0.0
Auto Prune Posts: common questions
Does Auto Prune Posts have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in Auto Prune Posts: 3 medium. None are known to affect version null.
How do I check which version of Auto Prune Posts I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Auto Prune Posts vulnerability?
CVE-2025-64262, published Nov 8, 2025: Auto Prune Posts <= 3.0.0 - Cross-Site Request Forgery. Severity: Medium (CVSS 4.3).
Is any Auto Prune Posts vulnerability listed in CISA KEV?
No. None of the known Auto Prune Posts vulnerabilities is currently listed in the CISA KEV catalog.