dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2024-3598

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 3.6.1 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 the plugin's Creative Button widget in all versions up to, and including, 3.6.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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 (versions up to 3.6.0) contains a stored XSS vulnerability in its Creative Button widget. Authenticated attackers with contributor-level access can inject malicious scripts through unsanitized user-supplied attributes, which then execute when other users access the affected pages.

MitigationUpdate ElementsKit Pro to the latest version after 3.6.0 which should contain proper patch. If no update available, consider temporarily disabling the Creative Button widget or using an alternative plugin until a patch is released.

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.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
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. Confirm ElementsKit Pro is installed
    Navigate to WordPress Admin > Plugins and locate 'ElementsKit Pro' in the installed plugins list.
    Affected if The plugin appears in the plugins list.
  2. Check the installed version number
    In the Plugins list, click on 'Details' for ElementsKit Pro or check the version displayed next to the plugin name.
    Affected if The version number shown is lower than 3.6.1.
  3. Identify pages using the Creative Button widget
    In the WordPress admin, search for posts/pages or use a plugin scanner to find where the ElementsKit Creative Button widget has been added to content.
    Affected if Any published or draft content contains the Creative Button widget.
  4. Inspect Creative Button widget settings for injected scripts
    Edit a page containing the Creative Button widget, open the widget settings, and examine all text fields (especially URL fields, text attributes, and custom CSS classes) for unusual characters, script tags, or event handlers like onload, onerror, or javascript:.
    Affected if Any attribute fields contain script tags, javascript: prefixes, or HTML event handlers.

You are affected if ElementsKit Pro version is below 3.6.1 AND the Creative Button widget is used on your site, particularly if untrusted contributor-level users have edit access.

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.1 or later
Fixed in 3.6.1
Interim mitigation

Update ElementsKit Pro to the latest version after 3.6.0 which should contain proper patch. If no update available, consider temporarily disabling the Creative Button widget or using an alternative plugin until a patch is released.

Recommended fix High confidence

3.6.1

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find ElementsKit Pro in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 3.6.1
  5. 5. Alternatively, go to Dashboard > Updates and update ElementsKit Pro from there
  6. 6. After updating, clear any caching plugins or server-side caches
  7. 7. Verify the update was successful by checking the plugin version

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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