WordPress security by component
Auto Prune Posts
Plugin description
Auto Prune Posts is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Nov 13, 2025; the highest published CVSS base score is 6.5.
Plugin slug:
auto-prune-postsLatest vulnerability
CVE-2025-64262: Auto Prune Posts: Cross-site request forgery
Auto Prune Posts is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Nov 13, 2025 |
CVE-2025-64262
Auto Prune Posts: Cross-site request forgery
Auto Prune Posts is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE6.5
NVDPending
|
| May 15, 2025 |
CVE-2024-10639
Auto Prune Posts: Cross-site scripting
Auto Prune Posts is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.8
NVDPending
|
| May 18, 2023 |
CVE-2023-27423
Auto Prune Posts: Cross-site request forgery
Auto Prune Posts is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.4
NVD8.8
|