Greenshift - Security Vulnerability (CVE-2026-120520)

Q: Am I affected by this vulnerability?

You are affected if your site runs Greenshift. No account is needed to exploit this, so a public site is reachable by anyone.

Q: How do I fix it?

Update Greenshift to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Restrict REST API in Hack Halt Pro contains this class of attack at the request layer.

Q: What can an attacker actually do?

This is a Information Disclosure flaw. An attacker who exploits it can read data they were never meant to see, which is often the first step in a larger attack.

CVE-2026-120520

Vulnerability CVE-2026-120520 PLUGIN greenshift MEDIUM

The Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 13.2.2 via the 'img (or any key the publisher references in {{GET:key}})' parameter. This makes it possible for unauthenticated attackers to extract authenticated users' HttpOnly WordPress session cookies, specifically wordpress_logged_in_* tokens, by injecting a nested {{COOKIE:}} placeholder via a GET parameter that causes the victim's browser to transmit the cookie value to an attacker-controlled host as an image src URL. Exploitation requires that a site publisher has configured a public GreenShift Element image block whose src attribute contains a {{GET:}} placeholder, and that a logged-in user can be induced to open the attacker's crafted link — neither condition is part of the plugin's default state.

CVE-2026-120520

MEDIUM CVSS 5.3 Published 2026-11-07 Updated 2026-11-08

AI Risk Elevated (60/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority

Severity Band MEDIUM

CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected Components 2

Reference Links 5

AI Risk Engine Elevated (60/100)

Exploitability High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-11-07 CVE published and first recorded in the threat feed.
2026-11-08 Record updated with latest vulnerability metadata.
2026-11-09 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 3 days ago

AI enriched 3 days ago (2026-11-09 15:06 UTC)

Technical Summary

Potential Impact

Severity is MEDIUM (CVSS 5.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 60/100 (Elevated, High) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Greenshift PLUGIN · greenshift Affected: <= 13.2.2 Fixed version not specified

Greenshift Animation And Page Builder Blocks PLUGIN · greenshift-animation-and-page-builder-blocks Affected: <= 13.2.2 Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Greenshift to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Restrict REST API in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Require authentication for REST namespaces that do not need to be public, so the API cannot be used to enumerate content and accounts.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Greenshift, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?