Skip to main content
VulnerabilityPublished

CVE-2026-5247: Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories (WordPress plugin) · Cross-site Scripting

Affects Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
publishpressSchedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change CategoriesAffected
  • <=4.10.0
Fixed in–

AI-suggested

Until an official fix is released, restrict administrator access to trusted users only and avoid enabling the vulnerable shortcode functionality for lower-privileged users. Monitor plugin updates from PublishPress for a security patch addressing this issue.

Description

The Schedule Post Changes With PublishPress Future WordPress plugin up to version 4.10.0 contains a stored cross-site scripting (XSS) vulnerability via the 'wrapper' attribute of the [futureaction] shortcode. This occurs because the plugin uses esc_html() to sanitize input, which does not prevent attribute injection when the value is used as an HTML tag name in a sprintf() call. Authenticated users with administrator privileges can inject arbitrary scripts that execute when other users view the affected pages. Since administrators can delegate this functionality to lower-privileged users, there is potential for abuse beyond administrators. No official patch or remediation guidance is currently available.

References

Community reviews

Loading reviews…