Plugins · auto-prune-posts · data as of 2026-11-04
Is Auto Prune Posts safe? Known vulnerabilities and latest version
- Latest version
- 3.1.1
- Last updated
- 2025-11-11
- Active installs
- 1,000+
- Known issues on record
- 3
- Unpatched in latest
- 0
- Tested up to WP
- 6.8.12
Auto deletes expires (prunes) posts after a certain amount of time. On a per category basis (single category, or all at once. — by ramon fincken
What to do
- Update to the latest version (3.1.1). Anything older than 3.1.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get auto-prune-posts --field=version shows what you run; wp plugin update auto-prune-posts updates it.
Check your version
Known vulnerabilities
3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.5 CVE-2025-64262 · published 2025-11-13
Cross-site request forgery (CSRF) in Auto Prune Posts (3.0.0 and older)
- Affected
- 3.0.0 and older
- Fixed in
- 3.1.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in ramon fincken Auto Prune Posts auto-prune-posts allows Cross Site Request Forgery.This issue affects Auto Prune Posts: from n/a through <= 3.0.0.
medium 4.8 CVE-2024-10639 · published 2025-05-15
Stored cross-site scripting (XSS) in Auto Prune Posts (older than 3.0.0)
- Affected
- older than 3.0.0
- Fixed in
- 3.0.0
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
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).
high 8.8 CVE-2023-27423 · published 2023-05-18
Cross-site request forgery (CSRF) in Auto Prune Posts (1.8.0 and older)
- Affected
- 1.8.0 and older
- Fixed in
- 2.0.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Ramon Fincken Auto Prune Posts plugin <= 1.8.0 versions.
Recent activity
- 2025-11-11 — latest release on wordpress.org (3.1.1).
- 2025-11-13 — Cross-site request forgery (CSRF) disclosed (CVE-2025-64262), fixed in 3.1.0.
- 2025-05-15 — Stored cross-site scripting (XSS) disclosed (CVE-2024-10639), fixed in 3.0.0.
- 2023-05-18 — Cross-site request forgery (CSRF) disclosed (CVE-2023-27423), fixed in 2.0.0.
Get an email when Auto Prune Posts has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Auto Prune Posts (auto-prune-posts) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site request forgery (CSRF) (2) · Cross-site scripting (XSS) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/auto-prune-posts (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/auto-prune-posts"><img src="https://laskyr.com/plugins/auto-prune-posts/badge.svg" alt="Auto Prune Posts vulnerability status"></a>