dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2371

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Insecure Direct Object Reference in all versions up to, and including, 12.8.3. This is due to missing authorization and post status validation in the `gspb_el_reusable_load()` AJAX handler. The handler accepts an arbitrary `post_id` parameter and renders the content of any `wp_block` post without checking `current_user_can('read_post', $post_id)` or verifying the post status. Combined with the nonce being exposed to unauthenticated users on any public page using the `[wp_reusable_render]` shortcode with `ajax="1"`, this makes it possible for unauthenticated attackers to retrieve the rendered HTML content of private, draft, or password-protected reusable blocks.

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 plugin's `gspb_el_reusable_load()` AJAX handler lacks authorization checks and post status validation, accepting any `post_id` parameter to render wp_block content. Combined with nonce exposure on public pages using the `[wp_reusable_render]` shortcode with `ajax='1'`, unauthenticated attackers can read private, draft, or password-protected reusable blocks.

MitigationUpdate to version 12.8.4 or later which adds proper authorization checks, nonce validation, and post status verification to the AJAX handler.

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 checks

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

  1. Check if Greenshift plugin is installed and identify its version
    In WordPress admin, go to Plugins > Installed Plugins and look for Greenshift - animation and page builder blocks. Note the version number displayed. Alternatively, check the plugin file header in wp-content/plugins/greenshift-animation-and-page-builder/greenshift.php
    Affected if Version is installed and is lower than 12.8.4 (the fixed version)
  2. Verify the vulnerable AJAX handler exists
    Check if the WordPress AJAX action gspb_el_reusable_load is registered. This can be done by searching the plugin files for 'add_action(\'wp_ajax_gspb_el_reusable_load' or 'gspb_el_reusable_load' AJAX hook registration, or by making a test AJAX request to /wp-admin/admin-ajax.php with action=gspb_el_reusable_load and a post_id parameter
    Affected if The AJAX action gspb_el_reusable_load is present and responds without requiring authentication or post ownership validation
  3. Determine if the shortcode exposes nonces
    Search WordPress public pages or page source for the [wp_reusable_render] shortcode with ajax='1' attribute. Check if this shortcode renders a nonce value in the page HTML that is visible to unauthenticated users. Inspect the rendered HTML of pages using this shortcode
    Affected if The shortcode [wp_reusable_render] with ajax='1' is used on public pages and outputs a nonce value in the HTML source that is accessible to unauthenticated visitors
  4. Identify protected wp_block content
    In WordPress admin, go to Posts > All Posts (or Blocks > Reusable Blocks depending on setup) and filter for wp_block post type. Look for blocks with status: Private, Draft, or Password Protected. Note their post IDs
    Affected if There are wp_block posts with private, draft, or password-protected status that could be targeted via the AJAX handler

The environment is affected if Greenshift plugin version is below 12.8.4 AND the gspb_el_reusable_load AJAX handler is active AND protected wp_block content exists that could be accessed without proper authorization.

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 version 12.8.4 or later which adds proper authorization checks, nonce validation, and post status verification to the AJAX handler.

Recommended fix Moderate confidence

Version 12.8.4 or later

  1. Check the current version of the Greenshift plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Greenshift – animation and page builder blocks and note the current version
  4. If the installed version is 12.8.3 or below, navigate to Dashboard > Updates or go to Plugins > Add New > Upload to install version 12.8.4 or later
  5. After upgrading, verify the fix by ensuring the `[wp_reusable_render]` shortcode no longer exposes the nonce to unauthenticated users when ajax="1" is set
  6. Test that private, draft, and password-protected wp_block posts are no longer accessible via the AJAX handler without proper authorization

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2371 — 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-2371 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