Greenshift Animation And Page Builder BlocksWordPress extension · Greenshiftwp
CVE-2024-6155
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 · uneditedThe Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to Authenticated (Subscriber+) Server-Side Request Forgery and Stored Cross Site Scripting in all versions up to, and including, 9.0.0 due to a missing capability check in the greenshift_download_file_localy function, along with no SSRF protection and sanitization on uploaded SVG files. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application that can also be leveraged to download malicious SVG files containing Cross-Site Scripting payloads to the server. On Cloud-based servers, attackers could retrieve the instance metadata. The issue was partially patched in version 8.9.9 and fully patched in version 9.0.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 · high confidenceThe Greenshift WordPress plugin has a critical vulnerability in the greenshift_download_file_localy function that allows authenticated users with Subscriber-level access to perform Server-Side Request Forgery (SSRF) attacks and upload malicious SVG files containing Cross-Site Scripting (XSS) payloads. The function lacks capability checks, SSRF protection, and SVG sanitization, enabling attackers to make arbitrary web requests from the server and upload files with embedded XSS.
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
< 9.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed Greenshift plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Greenshift Animation And Page Builder Blocks. Note the version number displayed. Alternatively, check the plugin's main PHP file header or version.php for the Version constant.Affected if The displayed version is lower than 9.0.1 (for example, 9.0.0, 8.x, or earlier)
-
Verify the vulnerable function exists in the plugin codeIn the WordPress wp-content/plugins/greenshift-animation-and-page-builder-blocks directory, search for the string 'greenshift_download_file_localy' in PHP files. Use grep, a file search, or open the plugin files to search for this function name.Affected if The function 'greenshift_download_file_localy' is found in the plugin code (indicates the vulnerable version is installed)
-
Confirm Subscriber-level user accounts existIn WordPress admin, go to Users > All Users. Review the list of users and their assigned roles. Check if any users have the 'Subscriber' role assigned.Affected if There are users with Subscriber-level access or any user role below Administrator exists in the system
-
Inspect for recently uploaded SVG filesNavigate to wp-content/uploads/ directory (or the configured upload path). Look for files with .svg extension, especially those uploaded recently or containing suspicious filenames. Check file contents for script tags, onload attributes, or XSS payloads.Affected if SVG files exist in the uploads directory, particularly files containing JavaScript code or suspicious content
-
Review server access logs for SSRF indicatorsExamine web server access logs (Apache, Nginx, or reverse proxy logs) for requests originating from the WordPress server to internal IP addresses such as 169.254.169.254 (cloud metadata endpoints), 127.0.0.1, or other internal network ranges.Affected if Outbound requests from the server appear in logs targeting internal/cloud metadata IPs or internal services
Your environment is likely affected if the Greenshift plugin version is below 9.0.1, the vulnerable function exists in the code, and Subscriber-level users can access file upload functionality.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.0.1
Update to Greenshift plugin version 9.0.1 or later. If immediate update is not possible, disable or restrict file upload functionality and monitor for suspicious requests to internal cloud metadata endpoints (169.254.169.254).
9.0.1
- Backup your WordPress site before making any changes
- Update the Greenshift – animation and page builder blocks plugin to version 9.0.1 or later through the WordPress admin dashboard (Plugins > All Plugins > Greenshift > Update Now)
- Verify the update was successfully applied by checking the plugin version in the installed plugins list
- Test the site's functionality to ensure the update did not break existing features
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
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6155 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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