dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2024-7064

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-15
Fix available
A fix is available. Upgrade to 3.6.6 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
The ElementsKit Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters in all versions up to, and including, 3.6.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 ElementsKit Pro WordPress plugin fails to properly sanitize user inputs and escape outputs in multiple parameters, allowing authenticated users with Contributor-level permissions to inject persistent malicious JavaScript. This stored XSS executes whenever other users view compromised pages.

MitigationUpdate ElementsKit Pro to version 3.6.6 or later. Alternatively, audit and sanitize all input parameters with functions like sanitize_text_field() and escape outputs with functions like esc_html() or esc_attr() before rendering.

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
ElementskitWordPress extension
Affected:< 3.6.6

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. Verify ElementsKit plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'ElementsKit' or 'ElementsKit Pro' in the plugin list.
    Affected if The plugin appears in the installed plugins list
  2. Check installed version against vulnerable range
    In the Plugins page, locate the version number displayed under the plugin name. Compare this version to the affected range: versions prior to 3.6.6 are vulnerable.
    Affected if The installed version is lower than 3.6.6 (e.g., 3.6.5, 3.5.0, etc.)
  3. Confirm contributor-level or higher user access exists
    Navigate to WordPress admin > Users. Review user roles assigned. Contributor role or higher (Editor, Author, Administrator) can exploit this flaw.
    Affected if There are user accounts with Contributor, Editor, Author, or Administrator roles active on the site
  4. Inspect pages built with ElementsKit for injected scripts
    View page source of published pages using ElementsKit widgets. Check for unexpected script tags, event handlers (onload, onerror, onmouseover), or iframe embeds in areas controlled by ElementsKit modules.
    Affected if Foreign JavaScript code or HTML tags appear in the rendered output of pages using ElementsKit widgets

A site is affected if it runs ElementsKit Pro version below 3.6.6 and has at least one user with Contributor-level permissions, with any injected scripts visible in page source.

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

Update ElementsKit Pro to version 3.6.6 or later. Alternatively, audit and sanitize all input parameters with functions like sanitize_text_field() and escape outputs with functions like esc_html() or esc_attr() before rendering.

Recommended fix High confidence

ElementsKit Pro version 3.6.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate ElementsKit Pro in the plugin list
  4. Check if an update is available (the plugin should show version 3.6.6 as the update)
  5. Click 'Update Now' to update ElementsKit Pro to version 3.6.6
  6. Alternatively, go to Dashboard > Updates and update all plugins including ElementsKit Pro
  7. After update, verify the plugin version shows 3.6.6 under Plugins > Installed Plugins

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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