CVE-2026-2589
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Greenshift WordPress plugin versions up to 12.8.3 stores automated settings backups containing sensitive API keys (OpenAI, Claude, Google Maps, Gemini, DeepSeek, Cloudflare Turnstile) in a publicly accessible file, allowing unauthenticated attackers to retrieve these credentials via direct URL access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Greenshift plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find Greenshift. Check the version number displayed, or inspect the plugin header in /wp-content/plugins/greenshift-animation-and-animation-library/readme.txtAffected if The installed version is 12.8.3 or lower (versions up to 12.8.3 are affected)
-
Locate automated backup filesCheck the plugin directory (/wp-content/plugins/greenshift-animation-and-animation-library/) and any backup folders for files with names containing 'backup', 'settings', 'automated', or similar patterns. Also check /wp-content/uploads/ for any recently created backup filesAffected if Any backup files exist in publicly accessible web directories
-
Test backup file accessibilityAttempt to access potential backup file URLs directly via browser (e.g., construct URLs like /wp-content/plugins/greenshift-.../backup*.json or similar patterns). If the file downloads or displays without authentication, it is publicly accessibleAffected if Backup files are reachable via direct HTTP request without authentication
-
Inspect backup content for API keysOpen any found backup files and search for strings like 'openai', 'claude', 'google_maps', 'gemini', 'deepseek', 'cloudflare_turnstile', 'api_key', or 'secret' to identify stored credentialsAffected if The backup files contain any API keys or secrets for the listed services
A user is affected if the Greenshift plugin version is 12.8.3 or lower AND automated backup files exist and are publicly accessible, as these files may expose API credentials to unauthenticated attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to version 12.8.4 or later to patch the vulnerability, or immediately restrict access to any backup files via web server configuration (e.g., .htaccess rules) and rotate any exposed API keys.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2589 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data