dbcve.org
GreenshiftWordPress extension · Wpsoul

CVE-2024-44005

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 9.4 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 <= 9.3.7.

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

A Stored Cross-Site Scripting (XSS) vulnerability exists in the Greenshift WordPress plugin (greenshift-animation-and-page-builder-blocks) due to improper input neutralization during web page generation. The vulnerability allows malicious scripts to be stored in the plugin's data and executed when other users view the affected pages.

MitigationUpdate to a patched version of Greenshift (version 9.3.8 or higher) which implements proper input sanitization and output encoding. If immediate update is not possible, implement additional output escaping on the affected plugin components and restrict user access to plugin settings.

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
GreenshiftWordPress extension
Affected:< 9.4

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. Verify Greenshift plugin installation
    Navigate to WordPress admin > Plugins and locate 'Greenshift - animation and page builder blocks' in the list of installed plugins. Confirm the plugin is activated.
    Affected if The Greenshift plugin is installed and activated in WordPress.
  2. Check installed Greenshift version
    In WordPress admin > Plugins, find the Greenshift plugin entry and read the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The installed version is lower than 9.4 (for example, 9.3.7, 9.3, 9.2.x, etc.).
  3. Identify stored data fields in plugin settings
    Access Greenshift plugin settings via WordPress admin menu. Look for any input fields where text, code snippets, or custom values can be saved and stored in the database, such as global settings, custom block configurations, or animation presets.
    Affected if The plugin contains settings or input fields that save user-supplied data to the WordPress database.
  4. Inspect stored plugin data in database
    Using a database tool (phpMyAdmin or WP-CLI), query the wp_postmeta or wp_options table for entries containing 'greenshift' in the meta_key or option_name. Examine stored values for any injected script tags or HTML attributes.
    Affected if The database contains stored values from Greenshift that include unescaped HTML/script content.
  5. Review rendered page source for unescaped output
    View a page built with Greenshift blocks on the frontend. Right-click and select 'View Page Source'. Search for any instances where user-entered text from plugin settings appears as raw HTML without entity encoding (for example, look for unescaped <script> tags, event handlers like onload/onerror, or raw quote characters in attributes).
    Affected if Greenshift-rendered content displays stored data without proper HTML entity encoding, allowing script execution.

A user is affected if the Greenshift plugin version is below 9.4 AND the plugin is actively storing user-supplied data that gets rendered without output encoding on the frontend.

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 9.4 or later
Fixed in 9.4
Interim mitigation

Update to a patched version of Greenshift (version 9.3.8 or higher) which implements proper input sanitization and output encoding. If immediate update is not possible, implement additional output escaping on the affected plugin components and restrict user access to plugin settings.

Recommended fix High confidence

Version 9.4 or later

  1. 1. Backup your WordPress site before updating
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find Greenshift (greenshift-animation-and-page-builder-blocks) in the plugin list
  4. 4. Click 'Update Now' if an update is available, or manually update to version 9.4 or later
  5. 5. After updating, verify the plugin version shows 9.4 or higher
  6. 6. Clear any caching plugins or server-side caches
  7. 7. Test that the Greenshift builder functionality works correctly after the update
Caveat Review changelog for any template/setting changes between your current version and 9.4 before updating in production

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

Fix this in Greenshift Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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