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

CVE-2026-1275

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 Multi Post Carousel by Category plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'slides' shortcode attribute in all versions up to, and including, 1.4. This is due to insufficient input sanitization and output escaping on the user-supplied 'slides' parameter in the post_slides_shortcode function. 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 Multi Post Carousel by Category WordPress plugin fails to sanitize and escape the 'slides' parameter in its post_slides_shortcode function, allowing authenticated users with Contributor+ permissions to inject malicious JavaScript that executes in browsers of users viewing affected pages.

MitigationUpdate to a patched version when available; otherwise, add proper input validation and sanitization for the 'slides' shortcode attribute plus output escaping where the value is rendered.

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. Verify the plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Multi Post Carousel by Category' in the list of active plugins.
    Affected if The plugin is installed and activated
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin name or view the plugin details to find the version number displayed alongside the plugin name.
    Affected if The installed version falls within an affected range that has not received a security patch for the shortcode vulnerability
  3. Check for use of the vulnerable shortcode
    Search your WordPress posts, pages, and custom post types for the [post_slides] shortcode, particularly looking for any usage that includes the 'slides' attribute.
    Affected if The [post_slides] shortcode with a 'slides' attribute is present in any published content
  4. Inspect shortcode attribute handling
    If you have file access, locate the plugin file containing the post_slides_shortcode function and verify whether the 'slides' parameter is being sanitized before output.
    Affected if The 'slides' parameter is rendered without proper escaping or sanitization

A user is affected if the Multi Post Carousel by Category plugin is installed with an unpatched version and the [post_slides] shortcode with a 'slides' attribute is in use 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 to a patched version when available; otherwise, add proper input validation and sanitization for the 'slides' shortcode attribute plus output escaping where the value is rendered.

Recommended fix Moderate confidence

Version 1.5 or latest available version of Multi Post Carousel by Category

  1. Identify the current version of the Multi Post Carousel by Category plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate 'Multi Post Carousel by Category' in the plugin list
  4. Check if the current version is 1.4 or below
  5. If vulnerable, update the plugin to the latest available version (version 1.5 or later, if available)
  6. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload a fixed version if manual update is required
  7. After updating, verify the fix by confirming the 'slides' shortcode attribute properly sanitizes and escapes user input
  8. Test by using the shortcode with a benign script payload to confirm it is no longer executed

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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