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

CVE-2026-4334

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-28
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 Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'headline' parameter in the [shariff] shortcode in all versions up to, and including, 4.6.20 due to insufficient input sanitization and output escaping. 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. The vulnerability occurs because the plugin uses a custom wp_kses implementation with permissive allowed HTML tags, and then performs a str_replace operation that injects HTML after sanitization, allowing event handlers to be introduced through the %total placeholder in the style attribute.

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 Shariff Wrapper WordPress plugin up to 4.6.20 suffers from a stored XSS vulnerability in the 'headline' parameter of the [shariff] shortcode. Authenticated attackers with Contributor-level access can inject arbitrary JavaScript via the headline parameter due to insufficient sanitization and output escaping. The vulnerability stems from a custom wp_kses implementation that is bypassed through a str_replace operation which injects HTML containing event handlers via the %total placeholder in the style attribute.

MitigationUpgrade to version 4.6.21 or later. As an interim measure, restrict the 'Contributor' role capabilities and audit existing posts using the shariff shortcode for malicious headline parameters.

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 the installed Shariff Wrapper plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'Shariff Wrapper' and read the version number displayed beneath the plugin name. Compare this to the affected range (versions 4.6.20 and below).
    Affected if The installed version is 4.6.20 or lower.
  2. Locate content using the shariff shortcode
    Query your WordPress database for posts/pages containing the '[shariff]' shortcode. In MySQL: SELECT ID, post_title, post_content FROM wp_posts WHERE post_content LIKE '%[shariff%' AND post_status IN ('publish', 'draft', 'pending');
    Affected if Any posts or pages contain the [shariff] shortcode.
  3. Inspect shortcode headline parameters for XSS payloads
    Examine the post_content for 'headline=' within shariff shortcodes. Look specifically for patterns involving %total placeholder in style attributes, such as 'headline=%total style=...'. Manually review each shortcode usage for unsanitized input.
    Affected if The headline parameter contains raw user input without proper encoding, or contains patterns like 'style=' followed by event handlers.
  4. Audit Contributor-level user accounts
    Review WordPress users with the Contributor role. Navigate to Users > All Users and filter by role 'Contributor'. Check their published content for any [shariff] shortcodes they may have inserted.
    Affected if There are Contributor users who have created or edited content containing shariff shortcodes.

A user is affected if the Shariff Wrapper plugin version is 4.6.20 or lower AND any content exists using the [shariff] shortcode with a headline parameter that may contain unsanitized input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 4.6.21 or later. As an interim measure, restrict the 'Contributor' role capabilities and audit existing posts using the shariff shortcode for malicious headline parameters.

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