← WordPress Vulnerabilities
WordPress security by component

Shariff Wrapper

Shariff Wrapper is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published May 28, 2026; the highest CVE/CNA score is 9.8.

Plugin slug: shariff

CVE-2026-4334: Shariff Wrapper: Cross-site scripting

Shariff Wrapper is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 4.6.20.

PublishedMay 28, 2026
Known safe version> 4.6.20
Safe version
May 28, 2026 CVE-2026-4334
Shariff Wrapper: Cross-site scripting
Shariff Wrapper is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 4.6.20.
> 4.6.20
CVE6.4
NVDPending
Jun 20, 2024 CVE-2024-4098
Shariff Wrapper: Filesystem traversal
Shariff Wrapper is affected by filesystem traversal. The vulnerable path is reachable without authentication. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
See mitigation notes
CVE9.8
NVDPending
Mar 21, 2024 CVE-2024-1450
Shariff Wrapper: Cross-site scripting
Shariff Wrapper is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4
Mar 21, 2024 CVE-2024-0966
Shariff Wrapper: Cross-site scripting
Shariff Wrapper is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4
Mar 19, 2024 CVE-2024-29109
Shariff Wrapper: Cross-site scripting
Shariff Wrapper 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.
See mitigation notes
CVE6.5
NVD5.4