dbcve.org
Skt Addons For ElementorWordPress extension · Sktthemes

CVE-2024-34436

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

Stored XSS vulnerability in SKT Addons for Elementor plugin allows attackers to inject malicious JavaScript via unsanitized input fields. The payload is stored in the database and executes when users view affected pages in the Elementor page builder.

MitigationUpdate SKT Addons for Elementor to version 1.9 or later which contains the security patch. Until patched, restrict access to the plugin or disable it if possible.

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
    Check your WordPress plugins directory or use WP-CLI: wp plugin list --search='skt-addons' to list installed plugins containing 'skt' in the name
    Affected if The plugin is present in the installation
  2. Determine installed plugin version
    Navigate to WordPress Admin > Plugins > SKT Addons for Elementor and view the version number in the plugin details, or use: wp plugin get skt-addons-for-elementor --field=version
    Affected if Version is lower than 1.9 (e.g., 1.8, 1.7, etc.)
  3. Confirm plugin is active
    Check if the plugin status is 'Active' in WordPress Admin > Plugins, or run: wp plugin list --status=active --search='skt-addons'
    Affected if Plugin is active and version is below 1.9
  4. Inspect Elementor-related database tables for suspicious stored scripts
    Query the WordPress postmeta and posts tables for any stored JavaScript tags (<script>, javascript:, onerror=, onload=) in Elementor-related custom post type entries or meta fields, especially in fields that may map to SKT Addons widgets
    Affected if Malicious script tags are found stored in the database associated with Elementor content
  5. Review Elementor editor page loads for unexpected script execution
    Open pages built with Elementor in the page builder editor mode and check browser developer console for any script errors or unexpected JavaScript execution originating from SKT Addons widgets
    Affected if JavaScript executes unexpectedly in the Elementor editor context

You are affected if SKT Addons for Elementor version below 1.9 is installed and active, and either stored XSS payloads exist in your database or anomalous scripts execute when editing pages with the plugin.

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 SKT Addons for Elementor to version 1.9 or later which contains the security patch. Until patched, restrict access to the plugin or disable it if possible.

Recommended fix Moderate confidence

1.9

  1. Create a full backup of your WordPress site before making any changes
  2. Navigate to WordPress dashboard > Plugins > Installed Plugins
  3. Find 'SKT Addons for Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.9 or later from the WordPress repository
  5. After updating, clear any caching plugins or server-side caches
  6. Verify the plugin version shows 1.9 or higher in the plugins list
  7. Test the affected functionality where the XSS vulnerability was reported to confirm the fix

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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