dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2127

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-18
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 SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to unauthorized arbitrary shortcode execution in all versions up to, and including, 1.70.4. This is due to a missing capability check on the `siteorigin_widget_preview_widget_action()` function which is registered via the `wp_ajax_so_widgets_preview` AJAX action. The function only verifies a nonce (`widgets_action`) but does not check user capabilities. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes by invoking the `SiteOrigin_Widget_Editor_Widget` via the preview endpoint. The required nonce is exposed on the public frontend when the Post Carousel widget is present on a page, embedded in the `data-ajax-url` HTML attribute.

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 SiteOrigin Widgets Bundle plugin's AJAX preview endpoint (`wp_ajax_so_widgets_preview`) validates only a nonce but lacks capability checks, allowing any authenticated user with Subscriber-level access to invoke the `SiteOrigin_Widget_Editor_Widget` and execute arbitrary shortcodes. The required nonce is exposed in the `data-ajax-url` attribute on public pages containing the Post Carousel widget.

MitigationUpdate to version 1.70.5 or later which adds proper capability checks to the preview AJAX action; alternatively, remove editor accounts with Subscriber-level access if updates are not feasible.

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. Identify SiteOrigin Widgets Bundle plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate SiteOrigin Widgets Bundle; note the version number displayed
    Affected if Version is earlier than 1.70.5 (the patched release)
  2. Detect Post Carousel widget usage
    Inspect public-facing pages and look for the Post Carousel widget, or search theme files and widget configurations for the 'siteorigin-panels-post-carousel' widget type
    Affected if Post Carousel widget is active on any public page, which exposes the preview nonce in the data-ajax-url attribute
  3. Check for subscriber-level user accounts
    Navigate to Users > All Users in WordPress admin and review the role column for accounts assigned the Subscriber role
    Affected if Any user account with Subscriber role exists in the system
  4. Verify AJAX endpoint accessibility
    Attempt a direct request to /wp-admin/admin-ajax.php?action=so_widgets_preview with a valid nonce (obtain from a page containing Post Carousel) while authenticated as a Subscriber-level user
    Affected if The request executes without returning a capability error, indicating the endpoint accepts the request without proper authorization

Your environment is affected if SiteOrigin Widgets Bundle version is below 1.70.5, the Post Carousel widget is in use exposing the nonce, and at least one Subscriber-level user account exists in WordPress.

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 1.70.5 or later which adds proper capability checks to the preview AJAX action; alternatively, remove editor accounts with Subscriber-level access if updates are not feasible.

Recommended fix Moderate confidence

1.70.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the SiteOrigin Widgets Bundle plugin
  4. Click 'Update now' if an update is available, or manually download and install version 1.70.5 or later
  5. Verify the update completed successfully

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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