dbcve.org
Reusable Blocks ExtendedWordPress extension · Jeanbaptisteaudras

CVE-2023-27611

HIGH · 8.8 CVSS v3.1 Published 2023-11-12
Fix available
A fix is available. Upgrade to after 0.9 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in audrasjb Reusable Blocks Extended plugin <= 0.9 versions.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Reusable Blocks Extended WordPress plugin (audrasjb) affecting versions 0.9 and below. The flaw allows attackers to trick authenticated administrators into unknowingly submitting malicious requests to the vulnerable plugin, potentially performing unauthorized actions such as modifying plugin settings or content.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations within the plugin and validate these tokens on the server side. Ensure proper Origin/Referer header validation. Update to the latest plugin version if a patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Reusable Blocks ExtendedWordPress extension
Affected:<= 0.9

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Reusable Blocks Extended plugin is installed
    Check WordPress plugins directory (wp-content/plugins/) for 'reusable-blocks-extended' folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if Plugin folder or entry exists in the WordPress plugins directory
  2. Check installed plugin version
    In WordPress admin, find 'Reusable Blocks Extended' in Plugins list and read the version number under the plugin name, or open the main plugin PHP file and look for 'Version:' in the plugin header comment
    Affected if Version displayed is 0.9 or lower
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify the plugin shows as 'Active'
    Affected if Plugin is activated on the site
  4. Identify state-changing admin actions without nonce protection
    Review plugin PHP files for form submissions and AJAX actions - search for functions that modify settings, content, or plugin data and check if they include wp_verify_nonce or check_admin_referer calls before processing
    Affected if Any admin actions (settings changes, content modifications, etc.) lack nonce validation logic

The environment is affected if Reusable Blocks Extended plugin is installed, active, and running version 0.9 or below, as CSRF protection is missing from state-changing operations.

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
Upgrade available Upgrade to a release after 0.9
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing operations within the plugin and validate these tokens on the server side. Ensure proper Origin/Referer header validation. Update to the latest plugin version if a patch is available.

Recommended fix Moderate confidence

Version 0.9.1 or later (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Reusable Blocks Extended' plugin
  4. Check if an update is available and update to the latest version (greater than 0.9)
  5. Alternatively, navigate to Dashboard > Updates and update all plugins
  6. Verify the update completed successfully

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

Fix this in Reusable Blocks Extended Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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