dbcve.org
GreenshiftWordPress extension · Wpsoul

CVE-2024-35765

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 8.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 (XSS or 'Cross-site Scripting') vulnerability in Wpsoul Greenshift – animation and page builder blocks allows Stored XSS.This issue affects Greenshift – animation and page builder blocks: from n/a through 8.8.9.1.

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 (animation and page builder blocks). The plugin fails to properly sanitize user input before rendering it in web pages, allowing attackers to inject malicious JavaScript that executes when other users view affected content.

MitigationUpgrade to a patched version of Greenshift (version 8.8.9.2 or later). Until a patch is available, implement Web Application Firewall rules to filter XSS payloads and review plugin admin panels for any suspicious injected content.

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:< 8.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. Check if Greenshift plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Greenshift' or 'Wpsoul Greenshift' in the list. Note the version number displayed next to the plugin name.
    Affected if Greenshift plugin is not found in the plugins list, so the vulnerability does not apply to this site.
  2. Verify the installed version
    Compare the installed version against the affected range: the vulnerability exists in versions before 8.9.4. Check the version displayed in the WordPress plugins list or in the plugin's main PHP file header.
    Affected if The installed version is 8.9.4 or higher, then the site is not affected by this specific CVE.
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Greenshift plugin status shows as 'Active'. Stored XSS only affects active installations.
    Affected if The plugin is deactivated, the stored XSS vulnerability cannot be triggered even if the vulnerable version is installed.
  4. Inspect Greenshift block content for injected scripts
    Review pages/posts using Greenshift blocks (animation blocks, page builder elements). Check the block content and settings for suspicious <script> tags, event handlers (onload, onerror, onmouseover), or encoded JavaScript in text fields. Also check the Greenshift plugin settings panels in WordPress admin.
    Affected if Malicious script tags or XSS payloads are found stored in Greenshift block content or plugin settings, indicating the vulnerability has been exploited.
  5. Review WordPress admin users and content
    Check Users > All Users for any unexpected administrator accounts that may have been created via XSS exploitation. Also review wp_posts table for any new pages with suspicious content containing script tags.
    Affected if Unexpected admin accounts exist or script-containing content was created, suggesting the stored XSS was used for privilege escalation or further attacks.

A site is affected if Greenshift (Wpsoul Greenshift) version below 8.9.4 is installed and active, with potential for malicious scripts to be present in block content or plugin settings.

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

Upgrade to a patched version of Greenshift (version 8.8.9.2 or later). Until a patch is available, implement Web Application Firewall rules to filter XSS payloads and review plugin admin panels for any suspicious injected content.

Recommended fix Moderate confidence

8.9.4 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the Greenshift – animation and page builder blocks plugin
  4. 4. Check if the current installed version is below 8.9.4
  5. 5. If vulnerable, click 'Update Now' to install version 8.9.4 or later
  6. 6. Verify the update completed successfully
  7. 7. Test the plugin functionality on your site to ensure proper operation
  8. 8. Clear any site caches if you use caching plugins

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

Fix this in Greenshift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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