dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2024-4452

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-21
Fix available
A fix is available. Upgrade to 3.6.2 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 ‘url’ parameter in versions up to, and including, 3.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions 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 has a stored XSS vulnerability in the 'url' parameter. Authenticated attackers with contributor-level permissions can inject malicious JavaScript through insufficient input sanitization on entry and inadequate output escaping on retrieval, causing scripts to execute in victims' browsers when they access affected pages.

MitigationUpgrade ElementsKit Pro to version 3.6.2 or later. Until then, limit contributor-level permissions and review existing pages for suspicious URL parameter values.

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

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 Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ElementsKit Pro' or check the /wp-content/plugins/elementskit-pro/ directory exists
    Affected if ElementsKit Pro plugin is present on the WordPress site
  2. Check installed version against affected range
    Navigate to Plugins > Installed Plugins > ElementsKit Pro and view the version number, or check the main plugin file header for the Version field
    Affected if The installed version is lower than 3.6.2
  3. Identify contributor-level user accounts
    Go to Users > All Users in WordPress admin and filter or search for users with the 'Contributor' role
    Affected if There are one or more user accounts with contributor-level permissions
  4. Inspect pages built with ElementsKit widgets
    Check the WordPress database or page editor for any pages/posts containing ElementsKit widgets that use URL parameters, particularly look for entries in postmeta tables where meta_key contains 'elementskit' and meta_value contains 'url='
    Affected if Pages exist that use ElementsKit widgets with URL parameter functionality and the stored value contains unsanitized script tags or javascript: URIs
  5. Review recent contributor-level post edits
    Check the wp_posts and wp_postmeta tables for recent posts edited by users with contributor role, focusing on any custom URL fields or links added through ElementsKit widgets
    Affected if Contributor users have recently created or edited content containing custom URL fields that may contain malicious script injection

A site is affected if it runs ElementsKit Pro versions below 3.6.2 and has contributor-level users who can access ElementsKit widgets with URL parameter functionality.

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.2 or later
Fixed in 3.6.2
Interim mitigation

Upgrade ElementsKit Pro to version 3.6.2 or later. Until then, limit contributor-level permissions and review existing pages for suspicious URL parameter values.

Recommended fix High confidence

3.6.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the ElementsKit Pro plugin
  4. Check if the current version is below 3.6.2
  5. If an update is available, click 'Update Now' to upgrade to version 3.6.2 or higher
  6. Alternatively, download ElementsKit Pro version 3.6.2 or newer from a trusted source and upload/install it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin version shows 3.6.2 or later

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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