dbcve.org
Skt Addons For ElementorWordPress extension · Sktthemes

CVE-2024-34445

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.9 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 ('Cross-site Scripting') vulnerability in SKT Themes SKT Addons for Elementor allows Stored XSS.This issue affects SKT Addons for Elementor: from n/a through 1.8.

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 · moderate confidence

Stored XSS vulnerability in SKT Addons for Elementor plugin allows attackers to inject malicious JavaScript code through unsanitized user input that gets stored in the database and executes when other users view affected pages in the Elementor page builder.

MitigationUpdate to a patched version of SKT Addons for Elementor when released; until then, implement WAF rules or disable the affected plugin components to block malicious script injection attempts.

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
Skt Addons For ElementorWordPress extension
Affected:< 1.9

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 SKT Addons for Elementor is installed
    Navigate to WordPress admin > Plugins and locate 'Skt Addons For Elementor' or 'SKT Addons for Elementor' in the plugin list. Confirm the plugin is active.
    Affected if The plugin is installed and active with a version below 1.9
  2. Check installed plugin version
    In the Plugins list, click on the plugin to view its details, or check the plugin header in wp-content/plugins/skt-addons-for-elementor/skt-addons-for-elementor.php for the 'Version' field. Compare the version number to the affected range (below 1.9).
    Affected if Installed version is less than 1.9 (for example, 1.8, 1.7, etc.)
  3. Identify plugin components accepting user input
    Review the plugin settings and widget configurations in Elementor editor. Look for any text input fields, form fields, or content areas provided by SKT Addons that accept user-generated content without visible sanitization indicators.
    Affected if Plugin features that accept and store user input are in use on pages/posts
  4. Inspect database for suspicious stored scripts
    Query the WordPress postmeta table (wp_postmeta) for meta_keys associated with SKT Addons widgets. Search for any stored values containing script tags, javascript:, or onload/onerror event handlers in the post content or meta tables.
    Affected if Database contains unsanitized script tags or event handler attributes in content created with SKT Addons components

If SKT Addons for Elementor is active at a version below 1.9 and contains user-supplied content in its widgets, the environment is potentially affected by stored XSS.

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.9 or later
Fixed in 1.9
Interim mitigation

Update to a patched version of SKT Addons for Elementor when released; until then, implement WAF rules or disable the affected plugin components to block malicious script injection attempts.

Recommended fix Moderate confidence

Version 1.9 or later

  1. Update SKT Addons for Elementor plugin to version 1.9 or later via WordPress plugin dashboard, FTP, or file upload
  2. Verify the update was successful by checking the installed plugin version
  3. Clear any site caches if caching plugins are in use

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

Fix this in Skt Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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