dbcve.org
Elementor Header\, Footer \& Blocks TemplateWordPress extension · Brainstormforce

CVE-2024-33933

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 1.6.36 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 (XSS or 'Cross-site Scripting') vulnerability in Brainstorm Force, Nikhil Chavan Elementor – Header, Footer & Blocks Template allows DOM-Based XSS.This issue affects Elementor – Header, Footer & Blocks Template: from n/a through 1.6.35.

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

DOM-based XSS vulnerability in the Elementor – Header, Footer & Blocks Template plugin allows injection of malicious scripts through unsanitized user input that reaches the page's DOM. The vulnerability exists in how the plugin handles input during web page generation, enabling attackers to execute arbitrary JavaScript in victims' browsers via crafted URLs.

MitigationUpdate the plugin to the latest version which should contain proper input sanitization for DOM manipulation. If no update is available, audit the plugin's JavaScript files for instances where user input flows into innerHTML, document.write, or similar DOM-modifying functions and apply context-aware output encoding.

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
Elementor Header\, Footer \& Blocks TemplateWordPress extension
Affected:< 1.6.36

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 the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Find 'Elementor - Header, Footer & Blocks Template' and note the version number displayed
    Affected if The installed version is any version before 1.6.36 (e.g., 1.6.35, 1.6.34, etc.)
  2. Verify the plugin is active
    In the same plugins list, confirm the 'Elementor - Header, Footer & Blocks Template' plugin shows as 'Active'
    Affected if The plugin is active and the version is below 1.6.36, the vulnerability is present in the runtime environment
  3. Identify template configurations using the plugin
    Navigate to Appearance > Header, Footer & Blocks (or the plugin's template settings page in WordPress admin) and review any active templates that render dynamic content
    Affected if Active templates exist and the plugin version is below 1.6.36, user-supplied input could be processed through vulnerable code paths
  4. Audit for DOM-manipulating code in the plugin
    Inspect the plugin's JavaScript files in wp-content/plugins/elementor-header-footer-blocks for instances where user input flows into innerHTML, outerHTML, document.write, or similar DOM-modifying functions (requires file access or a security scan)
    Affected if Such unsafe DOM manipulation patterns exist in the installed plugin version below 1.6.36

A user is affected if the Brainstormforce Elementor Header, Footer & Blocks Template plugin is installed with any version lower than 1.6.36 and is active in the WordPress environment.

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

Update the plugin to the latest version which should contain proper input sanitization for DOM manipulation. If no update is available, audit the plugin's JavaScript files for instances where user input flows into innerHTML, document.write, or similar DOM-modifying functions and apply context-aware output encoding.

Recommended fix High confidence

Elementor – Header, Footer & Blocks Template version 1.6.36 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Elementor – Header, Footer & Blocks Template' in the plugin list
  4. Check the current version installed
  5. If the version is below 1.6.36, click 'Update Now' to upgrade to version 1.6.36 or later
  6. Alternatively, navigate to Dashboard > Updates and update all plugins including this one
  7. After update, verify the installed version is 1.6.36 or higher

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

Fix this in Elementor Header\, Footer \& Blocks Template 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-2024-33933 — 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-33933 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