HomeWordPress vulnerabilitiesSchedule Post Changes With PublishPress Future
Schedule Post Changes With PublishPress Future vulnerabilities
Schedule Post Changes With PublishPress Future has 5 known vulnerabilities in this database. The most recent published record is dated 5 May 2026.
- Known vulnerabilities
- 5
- Active installs
- 100,000+
- Latest version
- 4.10.5
- Last updated
- 8 Sep 2026
- Most recent
- 5 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-5247 | Medium 5.5 | Up to 4.10.0 | Fixed in a later version (latest 4.10.5) | 5 May 2026 |
| Broken access control CVE-2025-14718 | Medium 5.4 | Up to 4.9.3 | Fixed in a later version (latest 4.10.5) | 9 Jan 2026 |
| Broken access control CVE-2025-13741 | Medium 4.3 | Up to 4.9.2 | Fixed in a later version (latest 4.10.5) | 16 Dec 2025 |
| Broken access control CVE-2025-13149 | Medium 4.3 | Up to 4.9.1 | Fixed in a later version (latest 4.10.5) | 21 Nov 2025 |
| Broken access control CVE-2021-24783 | Medium 6.5 | Before 2.6.0 | Fixed in 2.6.0 | 8 Nov 2021 |
Read the published descriptions
- CVE-2026-5247, 5 May 2026
- The Schedule Post Changes With PublishPress Future plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wrapper' attribute of the [futureaction] shortcode in all versions up to, and including, 4.10.0. This is due to insufficient input sanitization on the wrapper attribute. The plugin uses esc_html() to escape the value, but esc_html() only encodes HTML entities and does not prevent attribute injection when the value is used as an HTML tag name in a sprintf() call. An attacker can inject event handler attributes via spaces in the wrapper value. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Since it is also possible for administrators to make this functionality available to lower-privileged users, this introduces the possibility of abuse by contributors. CVE record
- CVE-2025-14718, 9 Jan 2026
- The Schedule Post Changes With PublishPress Future plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.9.3. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with Contributor-level access and above, to create, update, delete, and publish malicious workflows that may automatically delete any post upon publication or update, including posts created by administrators. CVE record
- CVE-2025-13741, 16 Dec 2025
- The Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the getAuthors function in all versions up to, and including, 4.9.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to retrieve emails for all users with edit_posts capability. CVE record
- CVE-2025-13149, 21 Nov 2025
- The Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on the "saveFutureActionData" function in all versions up to, and including, 4.9.1. This makes it possible for authenticated attackers, with author level access and above, to change the status of arbitrary posts and pages via the REST API endpoint. CVE record
- CVE-2021-24783, 8 Nov 2021
- The Post Expirator WordPress plugin before 2.6.0 does not have proper capability checks in place, which could allow users with a role as low as Contributor to schedule deletion of arbitrary posts. CVE record
What to do if you run Schedule Post Changes With PublishPress Future
If you run Schedule Post Changes With PublishPress Future, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Schedule Post Changes With PublishPress Future vulnerabilities
Free. We email you when a new vulnerability is published for Schedule Post Changes With PublishPress Future, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.