dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12134

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-24
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 ZoloBlocks – Gutenberg Block Editor Plugin with Advanced Blocks, Dynamic Content, Templates & Patterns plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the update_popup_status() function in all versions up to, and including, 2.3.11. This makes it possible for unauthenticated attackers to enable/disable popups.

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 ZoloBlocks WordPress plugin is vulnerable to broken access control due to a missing capability check on the update_popup_status() function. This allows unauthenticated attackers to make direct AJAX or REST API calls to enable or disable popups without any authentication or authorization validation.

MitigationUpdate the plugin to version 2.3.12 or later which implements proper capability checks using current_user_can() before executing the update_popup_status() function. Until patched, consider disabling the plugin or blocking unauthenticated access to the affected endpoint.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm ZoloBlocks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ZoloBlocks' in the list. Alternatively, check the /wp-content/plugins/zoloblocks/ directory exists on the server.
    Affected if The ZoloBlocks plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, find ZoloBlocks in the Plugins list and hover over or click to view the plugin details - the version number will be displayed in the plugin metadata. Alternatively, check the main plugin file header in /wp-content/plugins/zoloblocks/zoloblocks.php for the 'Version' tag.
    Affected if The installed version is lower than 2.3.12 (the patched version)
  3. Verify unauthenticated access to the affected endpoint
    Send a direct HTTP POST request to the AJAX endpoint (typically /wp-admin/admin-ajax.php) or REST API endpoint with action=update_popup_status, without including any authentication cookies or headers. Use a tool like curl: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=update_popup_status' -d 'status=0'
    Affected if The request succeeds and returns a successful response without requiring authentication (no 401 or 403 error)
  4. Check for exposed AJAX action hook
    Inspect the plugin source code (zoloblocks.php) for the presence of 'add_action("wp_ajax_update_popup_status", ...)' and verify it does NOT have a corresponding 'add_action("wp_ajax_nopriv_update_popup_status", ...)' call which would properly gate unauthenticated access.
    Affected if The plugin registers the update_popup_status AJAX action without the nopriv prefix handling, allowing unauthenticated execution

A user is affected if ZoloBlocks is installed with a version lower than 2.3.12 and the update_popup_status AJAX/REST endpoint accepts unauthenticated requests.

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 the plugin to version 2.3.12 or later which implements proper capability checks using current_user_can() before executing the update_popup_status() function. Until patched, consider disabling the plugin or blocking unauthenticated access to the affected endpoint.

Recommended fix Moderate confidence

2.3.12 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the ZoloBlocks plugin
  4. Check if an update is available and update to the latest version (2.3.12 or higher)
  5. Alternatively, you can update by going to Dashboard > Updates and updating the ZoloBlocks plugin

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 / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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