dbcve.org
Build \& Control Block PatternWordPress extension · Themeperch

CVE-2024-1095

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to after 1.3.5.4 or later.
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 Build & Control Block Patterns – Boost up Gutenberg Editor plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the settings_export() function in all versions up to, and including, 1.3.5.4. This makes it possible for unauthenticated attackers to export the plugin's settings.

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 Build & Control Block Patterns WordPress plugin has a missing capability check on the settings_export() function, allowing unauthenticated users to export plugin settings. This is a broken access control vulnerability where the function does not verify user permissions before returning sensitive configuration data.

MitigationApply the vendor patch (version 1.3.5.5 or higher) which adds proper capability checks to the settings_export() function. Until then, consider disabling the plugin or restricting access at the web server level.

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
Build \& Control Block PatternWordPress extension
Affected:<= 1.3.5.4

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. Identify if the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Themeperch Build & Control Block Pattern' or check the plugin files in /wp-content/plugins/ for a directory named similarly to 'build-control-block-pattern' or 'tp-build-control'
    Affected if The plugin is present in the WordPress installation
  2. Check the installed version
    In WordPress admin plugins list, find the version listed under the plugin name, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if Version is 1.3.5.4 or lower
  3. Verify the vulnerable function exists
    Inspect the main plugin PHP file and search for the function 'settings_export' - this function should exist in versions <= 1.3.5.4 without capability checks
    Affected if The settings_export() function exists and lacks a current_user_capability check (such as 'manage_options' or 'edit_posts') before returning data
  4. Test unauthenticated access to export functionality
    Send a POST request to wp-admin/admin-ajax.php with action=tp_build_control_settings_export (or similar action name based on the plugin's AJAX hooks) without providing authentication cookies
    Affected if The request returns plugin settings data without requiring authentication
  5. Check WordPress logs for suspicious export activity
    Review access logs for repeated POST requests to admin-ajax.php with the settings export action parameter, particularly from unauthenticated IP addresses
    Affected if Unauthenticated requests to the export endpoint are logged

The environment is affected if the Themeperch Build & Control Block Pattern plugin version 1.3.5.4 or lower is installed and active, and the settings_export() function is accessible without authentication.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.5.4
Interim mitigation

Apply the vendor patch (version 1.3.5.5 or higher) which adds proper capability checks to the settings_export() function. Until then, consider disabling the plugin or restricting access at the web server level.

Fix this in Build \& Control Block Pattern Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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