dbcve.org
BlocksyWordPress extension · Creativethemes

CVE-2024-32961

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-25
Fix available
A fix is available. Upgrade to 2.0.34 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in creativethemeshq Blocksy blocksy.This issue affects Blocksy: from n/a through <= 2.0.33.

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

Stored Cross-site Scripting (XSS) vulnerability in the Blocksy WordPress theme allows attackers to inject malicious JavaScript through unsanitized user input that gets rendered in web pages. The vulnerability exists in Blocksy theme versions up to and including 2.0.33.

MitigationUpdate Blocksy theme to version 2.0.34 or later which contains the patch. If no update is available, apply input sanitization/validation to user-supplied data before rendering in pages.

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.34

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Blocksy theme version in WordPress admin
    Navigate to WordPress Dashboard > Appearance > Themes. Locate the Blocksy theme and view its details to see the installed version number.
    Affected if The displayed version is less than 2.0.34 (for example, 2.0.33, 2.0.32, etc.)
  2. Check Blocksy version via theme files
    Access the theme files via FTP or file manager. Open /wp-content/themes/blocksy/style.css and look for the 'Version:' header in the file comments at the top.
    Affected if The version listed is 2.0.33 or lower.
  3. Check Blocksy version via WP-CLI
    Run command: wp theme list --status=active --format=table (or wp theme get blocksy) to retrieve the active theme version.
    Affected if The reported version is below 2.0.34.

If the installed Blocksy theme version is 2.0.33 or any version lower than 2.0.34, the environment is affected by this stored XSS vulnerability.

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.34 or later
Fixed in 2.0.34
Interim mitigation

Update Blocksy theme to version 2.0.34 or later which contains the patch. If no update is available, apply input sanitization/validation to user-supplied data before rendering in pages.

Recommended fix High confidence

2.0.34

  1. Update the Blocksy theme to version 2.0.34 or later through the WordPress admin dashboard under Appearance > Themes, or via FTP by uploading the new theme files

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

Fix this in Blocksy Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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