dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-5247

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The PublishPress Future WordPress plugin contains a stored XSS vulnerability in the [futureaction] shortcode's wrapper attribute. The plugin uses esc_html() to sanitize the wrapper value, but this fails to prevent attribute injection when the value is used as an HTML tag name in a sprintf() call. Attackers can inject event handler attributes via spaces in the wrapper value, allowing arbitrary JavaScript execution in the context of affected pages.

MitigationUpdate to version 4.10.1 or later which includes proper sanitization of the wrapper attribute. In the interim, restrict shortcode usage to trusted administrators and review pages using the [futureaction] shortcode.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PublishPress Future plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'PublishPress Future' or check the plugin files in wp-content/plugins/plugin-directory-for-publishpress-future/ for version information in the main PHP file header
    Affected if Plugin is installed and version is less than 4.10.1
  2. Identify all uses of the [futureaction] shortcode
    Search WordPress database (wp_posts table) for content containing the string '[futureaction]' using SQL: SELECT ID, post_title, post_content FROM wp_posts WHERE post_content LIKE '%[futureaction]%' AND post_status IN ('publish', 'draft')
    Affected if Any published or draft content contains the [futureaction] shortcode
  3. Inspect wrapper attribute values in shortcode usage
    For each post/page found, examine the wrapper parameter in the shortcode (e.g., [futureaction wrapper="div"]). Look for values containing spaces, quotes, or patterns that could inject attributes like 'div onclick=', 'span onmouseover=', or similar event handlers
    Affected if The wrapper attribute contains spaces, unusual characters, or appears to inject additional HTML attributes

A user is affected if they have PublishPress Future installed with version lower than 4.10.1 and any published content uses the [futureaction] shortcode with a wrapper attribute.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 4.10.1 or later which includes proper sanitization of the wrapper attribute. In the interim, restrict shortcode usage to trusted administrators and review pages using the [futureaction] shortcode.

Recommended fix Moderate confidence

4.10.1 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Schedule Post Changes With PublishPress Future' plugin
  4. 4. If an update to version 4.10.1 or higher is available, click 'Update Now'
  5. 5. Alternatively, download version 4.10.1 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the wrapper attribute in any [futureaction] shortcodes no longer accepts injected event handlers

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5247 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data