dbcve.org
BlocksyWordPress extension · Creativethemes

CVE-2024-31382

HIGH · 8.8 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to 2.0.23 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 creativethemeshq Blocksy blocksy.This issue affects Blocksy: from n/a through <= 2.0.22.

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 Blocksy WordPress theme allows attackers to induce authenticated users to perform unintended actions by tricking them into visiting malicious links or pages. The lack or improper implementation of anti-CSRF tokens (nonces) in the theme's forms and AJAX handlers enables this attack vector.

MitigationUpdate Blocksy theme to the latest version (2.0.23 or later) which should include proper nonce implementation and CSRF token validation for all state-changing operations.

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
BlocksyWordPress extension
Affected:< 2.0.23

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. Identify installed Blocksy theme version
    In WordPress admin, go to Appearance > Themes and check the version number listed for the Blocksy theme, or inspect the style.css file in wp-content/themes/blocksy/ and look for the 'Version:' header
    Affected if The displayed version is lower than 2.0.23 (e.g., 2.0.22, 2.0.21, etc.)
  2. Verify nonce implementation in theme AJAX handlers
    Examine the theme's PHP files in wp-content/themes/blocksy/ for AJAX action handlers (typically in functions.php or dedicated ajax files). Search for 'wp_ajax' and check if each handler includes a nonce check using 'check_ajax_referer' or 'wp_verify_nonce' before processing requests
    Affected if AJAX handlers are found that process state-changing requests without verifying a nonce token
  3. Inspect form handling for nonce validation
    Review theme template files that contain HTML forms (such as those for settings, contact forms, or subscription forms). Check if each form includes a nonce field (wp_nonce_field) or if the form submission handler verifies a nonce
    Affected if Forms that modify data (settings, user submissions, etc.) lack nonce field generation or server-side nonce verification
  4. Check for CSRF protection in admin settings pages
    If the theme includes a settings/admin panel, locate the PHP files handling form submissions from these panels. Verify that admin pages use 'check_admin_referer' or 'wp_verify_nonce' when processing configuration changes
    Affected if Admin form submissions lack anti-CSRF token validation

You are affected if the installed Blocksy theme version is below 2.0.23 AND the theme contains forms or AJAX handlers that perform actions without verifying CSRF tokens (nonces).

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.0.23 or later
Fixed in 2.0.23
Interim mitigation

Update Blocksy theme to the latest version (2.0.23 or later) which should include proper nonce implementation and CSRF token validation for all state-changing operations.

Recommended fix Moderate confidence

Blocksy theme version 2.0.23

  1. Backup your WordPress site before making any changes
  2. Navigate to Appearance > Themes in WordPress admin
  3. If updating from WordPress theme repository: Find Blocksy theme and click Update
  4. If updating manually: Download Blocksy version 2.0.23 from the official source (creativethemes.com)
  5. Upload and replace the existing Blocksy theme folder via Appearance > Themes > Add New > Upload Theme
  6. Verify the updated version is showing as 2.0.23 in Themes section
  7. Clear any caching mechanisms (plugin cache, CDN cache, server-side cache) after update
  8. Test critical functionality on the site to ensure the theme update did not break any features

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

Fix this in Blocksy 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-31382 — 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-31382 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