CVE-2026-5247: Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories <= 4.10.0 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'wrapper' Shortcode Attribute
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 eschtml() to escape the value, but eschtml() 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5247?
The severity of CVE-2026-5247 is rated as high due to its potential for storing cross-site scripting attacks.
How do I fix CVE-2026-5247?
To fix CVE-2026-5247, update the PublishPress Schedule Post Changes With PublishPress Future plugin to version 4.10.1 or later.
What versions of the plugin are affected by CVE-2026-5247?
CVE-2026-5247 affects all versions of the PublishPress Schedule Post Changes With PublishPress Future plugin up to and including version 4.10.0.
Can CVE-2026-5247 be exploited remotely?
Yes, CVE-2026-5247 can be exploited remotely by an authenticated user with administrator privileges.
What type of vulnerability is CVE-2026-5247?
CVE-2026-5247 is classified as a stored cross-site scripting (XSS) vulnerability.