dbcve.org
Greenshift Animation And Page Builder BlocksWordPress extension · Greenshiftwp

CVE-2025-26884

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 10.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpsoul Greenshift greenshift-animation-and-page-builder-blocks allows Stored XSS.This issue affects Greenshift: from n/a through <= 10.8.

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 · moderate confidence

This is a Stored Cross-Site Scripting (XSS) vulnerability in the Greenshift WordPress plugin (greenshift-animation-and-page-builder-blocks). The vulnerability allows an attacker to inject malicious JavaScript code that gets stored in the database and executes when other users view the affected pages within the WordPress admin or frontend.

MitigationUpdate Greenshift to the latest version to receive the security patch. Additionally, implement output encoding and input sanitization for all user-supplied data rendered in the plugin's blocks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Greenshift Animation And Page Builder BlocksWordPress extension
Affected:< 10.9

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Check Greenshift plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Greenshiftwp Greenshift Animation And Page Builder Blocks' to see the installed version number, or check the plugin header in /wp-content/plugins/greenshift-animation-and-page-builder-blocks/greenshift.php
    Affected if The displayed version is below 10.9 (for example, 10.8, 10.7, etc.)
  2. Verify plugin is active
    Confirm the Greenshift plugin is currently activated in the WordPress plugins list
    Affected if The plugin shows as 'Active' status - an inactive plugin cannot be exploited
  3. Identify content using Greenshift blocks
    Search the WordPress posts/pages database for content containing the shortcode or block markup associated with Greenshift blocks, or use a plugin scanner to list all posts using Greenshift elements
    Affected if The site contains posts, pages, or custom post types that utilize Greenshift blocks (the XSS payload would be stored in these post contents)
  4. Inspect stored content for suspicious script tags
    Query the wp_posts table in the database for any script tags, javascript:, or onmouseover/onerror attributes within Greenshift-related content, or manually review pages built with Greenshift blocks for unexpected inline scripts
    Affected if Malicious JavaScript code is found embedded in post content where Greenshift blocks were used - this indicates the vulnerability has been exploited

Your environment is affected if the Greenshift plugin version is below 10.9 and the plugin is active with content using its blocks, as this allows stored XSS payloads to persist and execute for other users.

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
Upgrade available Upgrade to 10.9 or later
Fixed in 10.9
Interim mitigation

Update Greenshift to the latest version to receive the security patch. Additionally, implement output encoding and input sanitization for all user-supplied data rendered in the plugin's blocks.

Recommended fix Moderate confidence

10.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Greenshift - Animation and Page Builder Blocks' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 10.9 from the WordPress plugin repository
  5. Verify the update completes successfully
  6. Confirm the installed version shows 10.9 or higher

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

Fix this in Greenshift Animation And Page Builder Blocks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26884 — 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-2025-26884 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