dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4895

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GreenShift WordPress plugin has a stored XSS vulnerability in the gspb_greenShift_block_script_assets() function. This function uses str_replace() to insert 'fetchpriority="high"' before 'src=' attributes in image blocks with disablelazy enabled. Because str_replace operates on the raw HTML string without parsing, attackers can inject 'src=' into other HTML attributes (like class), causing the replacement string's double quotes to break out of attribute context and inject malicious attributes like onfocus with JavaScript payloads.

MitigationUpdate the GreenShift plugin to a version that implements proper HTML parsing instead of str_replace, or apply vendor-supplied security patch to prevent attribute context breakout.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GreenShift plugin installation and version
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named greenshift-animation-and-animation-library or similar. Open the main plugin PHP file and look for the 'Version' header in the plugin comments, or check readme.txt for the version number.
    Affected if The installed version is lower than the patched version (compare against the vendor's security release that addressed this vulnerability).
  2. Locate the vulnerable function in plugin code
    Search the plugin files for the string 'gspb_greenShift_block_script_assets' or 'fetchpriority="high"' using grep or a file search in the wp-content/plugins/greenshift directory.
    Affected if The function exists and uses str_replace() to inject fetchpriority without proper HTML parsing.
  3. Identify image blocks with disablelazy enabled
    Export the WordPress database or query wp_posts and wp_postmeta for blocks containing 'disablelazy' set to true, or use the WordPress block editor to inspect image block settings in pages/posts. Check theme or block pattern files for image blocks with this attribute.
    Affected if Any image blocks exist where the disablelazy option is enabled, as this triggers the vulnerable code path.
  4. Verify block content allows attribute injection
    Review post content in wp_posts where meta_value or post_content contains image blocks with custom class attributes. Look for any user-submitted content that could contain the 'src=' string within attribute values.
    Affected if User-accessible content input exists (comments, user profiles, front-end forms) that could include the 'src=' injection string in HTML attributes.

A user is affected if the GreenShift plugin is installed with a vulnerable version AND image blocks with disablelazy enabled exist in the content, allowing the str_replace-based attribute context breakout to occur.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the GreenShift plugin to a version that implements proper HTML parsing instead of str_replace, or apply vendor-supplied security patch to prevent attribute context breakout.

Recommended fix Moderate confidence

Latest version of GreenShift plugin (greater than 12.8.9)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'GreenShift - Animation and Page Builder Blocks' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository and upload it manually
  6. 6. After updating, verify the plugin version is greater than 12.8.9

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4895 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data