CVE-2026-2589

Greenshift – animation and page builder blocks <= 12.8.3 - Unauthenticated Sensitive Information Exposure via Settings Backup

2026-03-05 10:58
Quốc Huy (jtwings)

Strategic Overview

Status
Patched in 12.8.4
Affected Plugin
Greenshift – animation and page builder blocks
Affected Version
<= 12.8.3
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-2589
View all Greenshift – animation and page builder blocks vulnerabilities

At a glance

CVE-2026-2589 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Greenshift WordPress plugin, affecting versions <= 12.8.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 12.8.4; sites on affected versions should update now. Disclosed March 2026, reported by Quốc Huy (jtwings).

Vulnerability Overview

The Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 12.8.3 via the automated Settings Backup stored in a publicly accessible file. This makes it possible for unauthenticated attackers to extract sensitive data including the configured OpenAI, Claude, Google Maps, Gemini, DeepSeek, and Cloudflare Turnstile API keys.

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 privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Greenshift <= 12.8.3 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Greenshift the fix is 12.8.4: builds <= 12.8.3 are affected, anything from 12.8.4 onward is not.

Remediation

Update to version 12.8.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Greenshift 12.8.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2589https://www.wordfence.com/threat-intel/vulnerabilities/id/2be2e028-81b8-4fd9-8197-eccf391fee65https://nvd.nist.gov/vuln/detail/CVE-2026-2589

Related records

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