CVE-2026-5093

Greenshift <= 12.8.9 - Authenticated (Contributor+) Theme Settings Modification via 'gspb_update_global_wp_settings'

2026-08-21 00:00
Raihan Adi Arba

Strategic Overview

Status
Patched in 12.9.0
Affected Plugin
Greenshift – animation and page builder blocks
Affected Version
<= 12.8.9
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-5093
View all Greenshift – animation and page builder blocks vulnerabilities

At a glance

CVE-2026-5093 is a medium-severity Missing Authorization vulnerability in the Greenshift WordPress plugin, affecting versions <= 12.8.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 12.9.0; sites on affected versions should update now. Disclosed August 2026, reported by Raihan Adi Arba.

Vulnerability Overview

The GreenShift – Animation and Page Builder Blocks plugin for WordPress is vulnerable to unauthorized modification of data in versions up to, and including, 12.8.9. This is due to a missing capability check on the 'gspb_update_global_wp_settings' function that only verifies the 'edit_posts' capability instead of requiring administrative privileges. This makes it possible for authenticated attackers, with contributor-level access and above, to modify global WordPress theme color settings site-wide, leading to site defacement.

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-862: Missing Authorization

Greenshift <= 12.8.9 carries this weakness at gspb_update_global_wp_settings, and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Greenshift the fix is 12.9.0: builds <= 12.8.9 are affected, anything from 12.9.0 onward is not.

Remediation

Update to version 12.9.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Greenshift 12.9.0 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-5093https://www.wordfence.com/threat-intel/vulnerabilities/id/69911634-1281-487c-87f1-37f6e4b016c9https://nvd.nist.gov/vuln/detail/CVE-2026-5093

Related records

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