dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1927

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the greenshift_app_pass_validation() function in all versions up to, and including, 12.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve global plugin settings including stored AI API keys and modify plugin settings, including the injection of arbitrary web scripts via the 'custom_css' value (stored XSS). NOTE: This vulnerability was partially patched in version 12.6.

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 confidence

The Greenshift WordPress plugin has a missing capability check on the greenshift_app_pass_validation() function, allowing authenticated users with Subscriber-level access to retrieve global plugin settings including stored AI API keys and modify settings, including injecting stored XSS via the custom_css value.

MitigationUpdate to the latest plugin version and rotate any exposed AI API keys. Review user roles and permissions to ensure Subscriber-level accounts have appropriate access controls.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Greenshift plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Greenshift' or check the plugin files in /wp-content/plugins/greenshift-animation-and-design-library/ for version information in the main PHP file header
    Affected if Greenshift plugin is installed and the version has the vulnerable function without capability checks
  2. Identify installed Greenshift version
    Open the main plugin file (e.g., greenshift-animation-and-design-library.php) and locate the 'Version' header in the plugin comment block, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name LIKE '%greenshift%version%'
    Affected if Version is unknown or falls within a range where greenshift_app_pass_validation() lacks capability checks
  3. Locate the vulnerable function in plugin code
    Search the plugin directory for the function 'greenshift_app_pass_validation' using grep or a file search: grep -r 'greenshift_app_pass_validation' /path/to/wp-content/plugins/greenshift-animation-and-design-library/
    Affected if The function exists and does not contain current_user_can() or a capability check before executing sensitive operations
  4. Check for Subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the role column for any accounts assigned the Subscriber role, or query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%subscriber%'
    Affected if Any Subscriber-level accounts exist in the WordPress installation
  5. Inspect Greenshift plugin settings for modified values
    Navigate to Greenshift plugin settings pages in WordPress admin, or query the wp_options table for greenshift-related settings, specifically examining the custom_css field for suspicious JavaScript or script tags
    Affected if Settings contain unexpected custom_css values with injected script tags or AI API keys are exposed in settings that should be restricted

A user is affected if the Greenshift plugin is installed with a version containing the unguarded greenshift_app_pass_validation function and Subscriber-level user accounts exist with access to trigger the vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest plugin version and rotate any exposed AI API keys. Review user roles and permissions to ensure Subscriber-level accounts have appropriate access controls.

Recommended fix Moderate confidence

Latest version after 12.6 (confirm fixed version via WordPress plugin repository release notes)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'Greenshift – animation and page builder blocks' plugin.
  4. 4. Check the current installed version (should be 12.6 or earlier based on the vulnerability report).
  5. 5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository.
  6. 6. After updating, verify the greenshift_app_pass_validation() function now includes proper capability checks (e.g., current_user_can('manage_options')).
  7. 7. Review and rotate any AI API keys that may have been exposed, as they could have been accessed during any prior exploitation.
Caveat Review plugin changelog for any breaking changes between current version and latest release; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1927 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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