dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2024-5263

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-15
Fix available
A fix is available. Upgrade to 3.6.3 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 Motion Text and Table widgets in all versions up to, and including, 3.6.2 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

ElementsKit Pro WordPress plugin versions up to 3.6.2 contain a stored XSS vulnerability in the Motion Text and Table widgets due to insufficient input sanitization and output escaping on user-supplied attributes. Authenticated users with contributor-level access or higher can inject malicious JavaScript that executes when other users access affected pages.

MitigationUpdate ElementsKit Pro to version 3.6.3 or later which contains the vendor patch addressing proper input sanitization and output escaping. Review existing pages using Motion Text and Table widgets for any injected scripts.

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

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 plugin files for version information in the main plugin file header
    Affected if The plugin is not installed, the vulnerability does not apply
  2. Check installed version number
    In WordPress admin Plugins list, look at the version column for ElementsKit Pro, or inspect the main plugin file (elementskit-pro.php) for the 'Version:' header comment
    Affected if Version is 3.6.2 or lower (less than 3.6.3)
  3. Identify active Motion Text widgets
    In WordPress admin, go to Pages > All Pages and edit each page to check if the ElementsKit Motion Text widget is added via the Elementor page builder widget panel
    Affected if Any page uses the Motion Text widget with user-controlled attributes
  4. Identify active Table widgets
    In WordPress admin, go to Pages > All Pages and edit each page to check if the ElementsKit Table widget is added via the Elementor page builder widget panel
    Affected if Any page uses the Table widget with user-controlled attributes

User is affected if ElementsKit Pro version is below 3.6.3 AND pages contain Motion Text or Table widgets with user-supplied attributes that lack proper escaping.

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.3 or later
Fixed in 3.6.3
Interim mitigation

Update ElementsKit Pro to version 3.6.3 or later which contains the vendor patch addressing proper input sanitization and output escaping. Review existing pages using Motion Text and Table widgets for any injected scripts.

Recommended fix High confidence

ElementsKit Pro 3.6.3

  1. Backup your WordPress site before performing any updates
  2. Navigate to WordPress Admin Dashboard > Plugins
  3. Locate the ElementsKit Pro plugin in the plugin list
  4. Click 'Update now' when an update to version 3.6.3 is available, or manually download version 3.6.3 from a trusted source and upload it via 'Add New' > 'Upload Plugin'
  5. After updating, clear any caching plugins or server-side caches
  6. Verify the update was successful by confirming the plugin version shows 3.6.3
  7. Test the Motion Text and Table widgets to confirm they function correctly with the fix

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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