Shariff for WordPress: Cross-site scripting
Shariff for WordPress is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 1.0.11.
- Component
- Shariff for WordPress
- Plugin slug
shariff-for-wordpress-shariff-for- Affected
- <= 1.0.11
- Safe version
> 1.0.11- Published
- Jun 27, 2026
- Weakness
- Not assigned
This CVE was published Jun 27, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Shariff for WordPress to a release after 1.0.11, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Shariff for WordPress Shariff for WordPress plugin through 1.0.11 does not sanitize or escape the shariff_infourl setting before outputting it in the frontend HTML via the generateshariff() function, 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).
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N