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

CVE-2026-6672

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-06
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 Affiliate Program Suite — SliceWP Affiliates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shortcode attributes in all versions up to, and including, 1.2.7. This is due to insufficient input sanitization and output escaping on user-supplied attributes in the 'slicewp_affiliate_url' shortcode. 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 SliceWP Affiliates WordPress plugin contains a stored cross-site scripting vulnerability in the 'slicewp_affiliate_url' shortcode. The plugin fails to properly sanitize and escape user-supplied attributes, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript that executes when other users view affected pages.

MitigationUpdate to version 1.2.8 or later which contains proper input sanitization and output escaping for shortcode attributes; alternatively, restrict shortcode usage permissions until the patch is applied.

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 SliceWP Affiliates plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'SliceWP Affiliates' in the list of active plugins.
    Affected if The plugin is installed and active.
  2. Check installed plugin version
    In the Plugins list, click on 'SliceWP Affiliates' to view plugin details, or open /wp-content/plugins/slicewp/readme.txt and locate the 'Stable tag' or version number in the plugin header file /wp-content/plugins/slicewp/slicewp.php.
    Affected if The installed version is lower than 1.2.8.
  3. Identify pages using the shortcode
    Search the WordPress database: query wp_posts for content containing '[slicewp_affiliate_url' or use a plugin like 'Search Regex' to scan posts, pages, and custom post types for this shortcode.
    Affected if The shortcode [slicewp_affiliate_url] exists in any published content.
  4. Verify shortcode output is visible to visitors
    View a page containing the shortcode as a logged-out visitor or different user role. Inspect the rendered HTML to see if the shortcode attribute values appear unescaped in the output.
    Affected if The shortcode renders and its attributes are visible in page source without proper HTML escaping.
  5. Check user role permissions for content creation
    Navigate to Users > All Users in WordPress admin. Review which users have 'Contributor' or higher roles who can create or edit content containing shortcodes.
    Affected if There are users with Contributor-level or higher access who can create or edit posts containing the shortcode.

You are affected if SliceWP Affiliates plugin version is below 1.2.8, the [slicewp_affiliate_url] shortcode is used on your site, and users with Contributor-level permissions can access or edit content containing that shortcode.

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 1.2.8 or later which contains proper input sanitization and output escaping for shortcode attributes; alternatively, restrict shortcode usage permissions until the patch is applied.

Recommended fix Moderate confidence

Any version higher than 1.2.7 (check wordpress.org for current stable release)

  1. 1. Log in to the WordPress admin dashboard with contributor-level or higher privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'SliceWP Affiliates' (Affiliate Program Suite)
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/slicewp-affiliates/ and upload manually
  6. 6. After updating, verify the 'slicewp_affiliate_url' shortcode properly sanitizes and escapes user-supplied attributes

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-6672 — 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-6672 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