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

CVE-2026-4022

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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 Show Posts list – Easy designs, filters and more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_type' shortcode attribute in the 'swiftpost-list' shortcode in all versions up to, and including, 1.1.0 due to insufficient input sanitization and output escaping on user-supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 WordPress 'Show Posts list' plugin fails to sanitize and escape the 'post_type' attribute in the 'swiftpost-list' shortcode, allowing authenticated contributors+ to inject persistent JavaScript that executes when pages containing the shortcode are viewed.

MitigationUpdate the plugin to version 1.1.1 or later which implements proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on shortcode attributes.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if Show Posts list plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Show Posts list' or 'SwiftPost' plugin. Alternatively, check the wp-content/plugins directory for folders containing 'show-posts', 'swiftpost', or similar names.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In Plugins > Installed Plugins, click 'View Details' on the Show Posts list/SwiftPost plugin to see the version number. Compare against the affected range (versions prior to 1.1.1).
    Affected if The installed version is older than 1.1.1
  3. Check if the swiftpost-list shortcode is in use
    Search the WordPress database (wp_posts table) or use a plugin to search post content for the string '[swiftpost-list'. You can also check page source on frontend for presence of this shortcode rendered in content.
    Affected if The shortcode [swiftpost-list] is found in any post, page, or custom post type content
  4. Verify contributor+ user access exists
    In WordPress admin, go to Users and review user roles. Contributor, Author, Editor, and Administrator roles all have privileges sufficient to create or edit content containing the shortcode.
    Affected if There are users with Contributor, Author, Editor, or Administrator roles who can create or edit posts

You are affected if the Show Posts list/SwiftPost plugin version is below 1.1.1 AND the swiftpost-list shortcode is present in any content AND at least one user with Contributor-level access or higher exists on the site.

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 the plugin to version 1.1.1 or later which implements proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on shortcode attributes.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (any version above 1.1.0)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Show Posts list – Easy designs, filters and more' plugin
  4. Check the current installed version (should be 1.1.0 or below)
  5. Update the plugin to the latest available version from the WordPress plugin repository
  6. Verify the update completes successfully
  7. Test that the swiftpost-list shortcode functions correctly with the post_type attribute after updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4022 — 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-4022 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