Shariff Wrapper <= 4.6.20 - Authenticated (Contributor+) Cross-Site Scripting
Strategic Overview
- Status
- Patched in 4.6.21
- Affected Plugin
- Shariff Wrapper
- Affected Version
<= 4.6.20- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-4334
At a glance
CVE-2026-4334 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Shariff Wrapper WordPress plugin, affecting versions <= 4.6.20. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.6.21; sites on affected versions should update now. Disclosed May 2026, reported by Muhammad Yudha - DJ.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Shariff Wrapper <= 4.6.20 carries this weakness at headline, and reaching it takes an account at Contributor level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Shariff Wrapper the fix is 4.6.21: builds <= 4.6.20 are affected, anything from 4.6.21 onward is not.
Remediation
Update to version 4.6.21, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Shariff Wrapper 4.6.21 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2024-2695: Shariff Wrapper <= 4.6.13 Stored Cross-Site Scripting
CVE-2024-2695 - 6.4CVE-2024-1450: Shariff Wrapper <= 4.6.10 Stored Cross-Site Scripting
CVE-2024-1450 - 6.4CVE-2024-0966: Shariff Wrapper <= 4.6.9 Stored Cross-Site Scripting
CVE-2024-0966 - 6.4CVE-2023-6500: Shariff Wrapper <= 4.6.9 Stored Cross-Site Scripting
CVE-2023-6500
Other vulnerabilities in Shariff Wrapper
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C