CVE-2026-4895 Greenshift <= 12.8.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via disablelazy Attribute

Medium 6.4 Published Updated

Authenticated contributors can inject arbitrary JavaScript via the disablelazy attribute in the Greenshift WordPress plugin, leading to stored XSS.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-4895?

CVE-2026-4895 is a medium-severity cross-site scripting vulnerability in wpsoul Greenshift – animation and page builder blocks, published on 11 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

The GreenShift - Animation and Page Builder Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 12.8.9 This is due to insufficient input sanitization and output escaping in the gspb_greenShift_block_script_assets() function. The function uses str_replace() to insert 'fetchpriority="high"' before 'src=' attributes when processing greenshift-blocks/image blocks with the disablelazy attribute enabled. Because this replacement operates on the entire HTML string without parsing, contributors can inject the string 'src=' into HTML attribute values (such as class attributes). When the str_replace executes, the double quotes in the replacement string break out of the attribute context, allowing injection of malicious HTML attributes like onfocus with JavaScript payloads. 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.

Weakness: CWE-79

Which versions are affected by CVE-2026-4895?

How do I fix CVE-2026-4895?

No fix has been published for CVE-2026-4895 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-4895 being exploited?

There is no known exploitation of CVE-2026-4895 in the wild and no public exploit code.

Sources

Also known as GHSA-rmxh-6c8g-3v9r.

Is CVE-2026-4895 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free