Plugins · shariff · data as of 2026-11-04
Is Shariff Wrapper safe? Known vulnerabilities and latest version
- Latest version
- 4.6.22
- Last updated
- 2026-05-15
- Active installs
- 30,000+
- Known issues on record
- 8
- Unpatched in latest
- 0
- Tested up to WP
- 6.9.11 · PHP 7.4+
Shariff provides share buttons that respect the privacy of your visitors and follow the General Data Protection Regulation (GDPR). — by 3UU
What to do
- Update to the latest version (4.6.22). Anything older than 4.6.21 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get shariff --field=version shows what you run; wp plugin update shariff updates it.
Check your version
Known vulnerabilities
8 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.4 CVE-2026-4334 · published 2026-05-28
Stored cross-site scripting (XSS) in Shariff Wrapper (4.6.20 and older)
- Affected
- 4.6.20 and older
- Fixed in
- 4.6.21 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-4334Wordfence advisoryCode change (fix)Plugin source
critical 9.8 CVE-2024-4098 · published 2024-06-20
File inclusion in Shariff Wrapper (4.6.13 and older)
- Affected
- 4.6.13 and older
- Fixed in
- 4.6.14 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Shariff Wrapper plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 4.6.13 via the shariff3uu_fetch_sharecounts function. This allows unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
NVD CVE-2024-4098Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2024-2695 · published 2024-06-15
Stored cross-site scripting (XSS) in Shariff Wrapper (4.6.13 and older)
- Affected
- 4.6.13 and older
- Fixed in
- 4.6.14 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'shariff' shortcode in all versions up to, and including, 4.6.13 due to insufficient input sanitization and output escaping on user supplied attributes such as 'borderradius', 'services' and 'timestamp'. 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.
medium 5.4 CVE-2024-1450 · published 2024-03-21
Stored cross-site scripting (XSS) in Shariff Wrapper (4.6.10 and older)
- Affected
- 4.6.10 and older
- Fixed in
- 4.6.11 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'shariff' shortcode in all versions up to, and including, 4.6.10 due to insufficient input sanitization and output escaping on user supplied attributes such as 'align'. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE-2024-29109 appears to be a duplicate of this issue.
NVD CVE-2024-1450Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2024-0966 · published 2024-03-21
Stored cross-site scripting (XSS) in Shariff Wrapper (4.6.9 and older)
- Affected
- 4.6.9 and older
- Fixed in
- 4.6.10 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'shariff' shortcode in all versions up to, and including, 4.6.9 due to insufficient input sanitization and output escaping on user supplied attributes like 'info_text'. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page and clicks the information icon.
NVD CVE-2024-0966Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2023-6500 · published 2024-03-21
Stored cross-site scripting (XSS) in Shariff Wrapper (4.6.9 and older)
- Affected
- 4.6.9 and older
- Fixed in
- 4.6.10 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'shariff' shortcode in all versions up to, and including, 4.6.9 due to insufficient input sanitization and output escaping on user supplied attributes such as 'secondarycolor' and 'maincolor'. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
medium 5.4 CVE-2024-29109 · published 2024-03-19
Stored cross-site scripting (XSS) in Shariff Wrapper (4.6.10 and older)
- Affected
- 4.6.10 and older
- Fixed in
- 4.6.11
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Jan-Peter Lambeck & 3UU Shariff Wrapper allows Stored XSS.This issue affects Shariff Wrapper: from n/a through 4.6.10.
medium 6.1 CVE-2024-1106 · published 2024-02-27
Stored cross-site scripting (XSS) in Shariff Wrapper (older than 4.6.10)
- Affected
- older than 4.6.10
- Fixed in
- 4.6.10
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Shariff Wrapper WordPress plugin before 4.6.10 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
Recent activity
- 2026-05-15 — latest release on wordpress.org (4.6.22).
- 2026-05-28 — Stored cross-site scripting (XSS) disclosed (CVE-2026-4334), fixed in 4.6.21.
- 2024-06-20 — File inclusion disclosed (CVE-2024-4098), fixed in 4.6.14.
- 2024-06-15 — Stored cross-site scripting (XSS) disclosed (CVE-2024-2695), fixed in 4.6.14.
Get an email when Shariff Wrapper has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Shariff Wrapper (shariff) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (7) · File inclusion (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/shariff (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/shariff"><img src="https://laskyr.com/plugins/shariff/badge.svg" alt="Shariff Wrapper vulnerability status"></a>