CVE-2026-83543

Greenshift – animation and page builder blocks < 13.2.0 - Authenticated (Contributor+) Server-Side Request Forgery

2026-09-05 00:00
Alireza Kalhor

Strategic Overview

Status
Patched in 13.2.0
Affected Plugin
Greenshift – animation and page builder blocks
Affected Version
< 13.2.0
CVSS
6.4Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-83543
View all Greenshift – animation and page builder blocks vulnerabilities

At a glance

CVE-2026-83543 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Greenshift WordPress plugin, affecting versions < 13.2.0. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 13.2.0; sites on affected versions should update now. Disclosed September 2026, reported by Alireza Kalhor.

Vulnerability Overview

The Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to 13.2.0. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

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.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Greenshift < 13.2.0 takes an account at Contributor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Greenshift the fix is 13.2.0: builds < 13.2.0 are affected, anything from 13.2.0 onward is not.

Remediation

Update to version 13.2.0, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor 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. None of that substitutes for the fix: Greenshift 13.2.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-83543https://www.wordfence.com/threat-intel/vulnerabilities/id/732fb8ec-b520-4e24-a479-4c7be15b67f7https://nvd.nist.gov/vuln/detail/CVE-2026-83543

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C