Greenshift 11.4 - 11.4.5 - Authenticated (Subscriber+) Arbitrary File Upload
Strategic Overview
- Status
- Patched in 11.4.6
- Affected Plugin
- Greenshift – animation and page builder blocks
- Affected Version
11.4 – 11.4.5- CVSS
- 8.8High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-3616
At a glance
CVE-2025-3616 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Greenshift WordPress plugin, affecting versions 11.4 – 11.4.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 11.4.6; sites on affected versions should update now. Disclosed April 2025, reported by mikemyers.
Vulnerability Overview
The Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the gspb_make_proxy_api_request() function in versions 11.4 to 11.4.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. The arbitrary file upload was sufficiently patched in 11.4.5, but a capability check was added in 11.4.6 to properly prevent unauthorized limited file uploads.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Greenshift 11.4 – 11.4.5 carries this weakness at gspb_make_proxy_api_request(), and reaching it takes an account at Subscriber level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Greenshift the fix is 11.4.6: builds 11.4 – 11.4.5 are affected, anything from 11.4.6 onward is not.
Remediation
Update to version 11.4.6, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Greenshift 11.4.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Greenshift – animation and page builder blocks
- 6.4CVE-2026-83544: Greenshift Stored XSS
CVE-2026-83544 - 6.4CVE-2026-83543: Greenshift – animation and page builder blocks SSRF
CVE-2026-83543 - 6.4CVE-2026-5092: Greenshift <= 12.8.9 Stored Cross-Site Scripting
CVE-2026-5092 - 6.4CVE-2026-4895: Greenshift <= 12.8.9 Stored Cross-Site Scripting
CVE-2026-4895 - 6.4CVE-2026-2593: Greenshift Stored XSS
CVE-2026-2593 - 6.4CVE-2025-11841: Greenshift Stored XSS
CVE-2025-11841 - 6.4CVE-2025-49301: Greenshift <= 11.5.5 Stored Cross-Site Scripting
CVE-2025-49301 - 6.4CVE-2025-30873: Greenshift <= 11.0.2 Stored Cross-Site Scripting
CVE-2025-30873
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C