Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories
post-expirator · plugin
Known security vulnerabilities for Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
latest May 4, 2026
Listed on wordpress.org · latest 4.10.5 · last updated Sep 8, 2026 · 100K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Medium 6.5
CVE-2026-39482login required≤ 4.9.4
WordPress Post Expirator plugin <= 4.9.4 - Cross Site Scripting (XSS) vulnerability
- Medium 5.5
CVE-2026-5247admin≤ 4.10.0
Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories <= 4.10.0 - Authenticated (Administrator+) Stored Cro
- Medium 5.4
CVE-2025-14718contributor+≤ 4.9.3
Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories <= 4.9.3 - Missing Authorization to Authenticated (Co
- Medium 4.3
CVE-2025-69361login required≤ 4.9.3
WordPress Post Expirator plugin <= 4.9.3 - Broken Access Control vulnerability
- Medium 4.3
CVE-2025-13741contributor+≤ 4.9.2
Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories <= 4.9.2 - Missing Authorization to Authenticated (Co
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).