dbcve.org
BricksforgeWordPress extension

CVE-2024-31244

HIGH · 7.5 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
84/100
Remediation priority · High
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
Missing Authorization vulnerability in Bricksforge.This issue affects Bricksforge: from n/a through 2.0.17.

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

Missing Authorization vulnerability in Bricksforge plugin versions through 2.0.17 allows unauthenticated or unauthorized users to access sensitive functionality or perform actions that should require proper authentication and capability checks.

MitigationUpdate Bricksforge to version 2.0.18 or later which contains the authorization fix. Review access controls and implement proper capability checks and nonce verification on sensitive endpoints.

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
BricksforgeWordPress extension
Affected:< 2.1.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check Bricksforge plugin version
    In WordPress admin, navigate to Plugins > Installed Plugins and locate Bricksforge to view the version number, or read the Version field from the plugin header in wp-content/plugins/bricksforge/bricksforge.php
    Affected if Version is 2.0.17 or earlier (versions through 2.0.17 are affected)
  2. Confirm Bricksforge is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that Bricksforge shows as Active
    Affected if Plugin is active on the site and version is below 2.1.1
  3. Test AJAX endpoint access without authentication
    Send unauthenticated GET or POST requests to Bricksforge AJAX actions at /wp-admin/admin-ajax.php?action=bricksforge_* using curl or browser developer tools
    Affected if Endpoints return sensitive data or perform actions without requiring login or capability verification
  4. Check access to sensitive functionality
    Attempt to access Bricksforge-related pages, settings, or builder functionality from a browser session where you are logged out or logged in as a low-privilege user
    Affected if Sensitive functionality is accessible without proper authentication or capability checks

Environment is affected if Bricksforge version is 2.0.17 or earlier and sensitive functionality can be accessed without authentication or proper authorization checks.

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 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Update Bricksforge to version 2.0.18 or later which contains the authorization fix. Review access controls and implement proper capability checks and nonce verification on sensitive endpoints.

Recommended fix High confidence

Bricksforge 2.1.1

  1. 1. Create a complete backup of your WordPress site (database and files)
  2. 2. Update Bricksforge plugin to version 2.1.1 or later through the WordPress admin dashboard (Plugins > Updates) or via WP-CLI: wp plugin update bricksforge
  3. 3. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  4. 4. Test critical site functionality to ensure the update did not break existing features
  5. 5. Confirm the authorization controls are functioning properly by testing affected functionality

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

Fix this in Bricksforge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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