dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-2303

HIGH · 8.8 CVSS v3.1 Published 2025-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Block Logic – Full Gutenberg Block Display Control plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.0.8 via the block_logic_check_logic function. This is due to the unsafe evaluation of user-controlled input. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.

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 Block Logic WordPress plugin (versions up to 1.0.8) is vulnerable to Remote Code Execution due to unsafe evaluation of user-controlled input in the block_logic_check_logic function. Authenticated attackers with Contributor-level access or higher can execute arbitrary code on the server by supplying malicious input that gets evaluated.

MitigationUpdate the plugin to version 1.0.9 or later which contains the security patch. If an update is unavailable, immediately remove the plugin and restrict user permissions to Administrator level only until remediation is possible.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Locate the Block Logic plugin installation
    Check your WordPress wp-content/plugins/ directory for a folder named 'block-logic' or similar. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to confirm the Block Logic plugin is present.
    Affected if The Block Logic plugin is installed on the WordPress site.
  2. Identify the installed plugin version
    Open the main plugin file (usually block-logic.php or similar in the plugin folder) and look for the version comment in the file header, or check the plugin details displayed in the WordPress admin Plugins page.
    Affected if The version number found is 1.0.8 or earlier.
  3. Verify the vulnerable function exists
    Search the plugin PHP files for the function named 'block_logic_check_logic' and inspect whether it contains eval(), create_function(), or similar dynamic code execution functions.
    Affected if The function exists and uses eval() or equivalent to process user input.
  4. Confirm attack surface through user roles
    Review WordPress user roles and permissions on the site. Check if any user accounts exist with Contributor-level access or higher, as this privilege is required to exploit the vulnerability.
    Affected if Any user with Contributor, Author, Editor, or Administrator role exists on the site.

You are affected if the Block Logic plugin is installed with version 1.0.8 or earlier and the block_logic_check_logic function uses unsafe evaluation, regardless of which authenticated users exist on the site.

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 1.0.9 or later which contains the security patch. If an update is unavailable, immediately remove the plugin and restrict user permissions to Administrator level only until remediation is possible.

Recommended fix Moderate confidence

Version 1.0.9 or latest available version from wordpress.org/plugins/block-logic

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Block Logic – Full Gutenberg Block Display Control'
  4. Check if the current version is 1.0.8 or lower
  5. If vulnerable, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/block-logic and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the fix

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-2303 — 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-2303 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