Skt Addons For ElementorWordPress extension · Sktthemes

CVE-2024-38674

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-20

Fix available

A fix is available. Upgrade to 3.2 or later.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

Improper Neutralization of Input During Web Page Generation (XSS or '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 3.0.

Technical summary

dbcve analysis · moderate confidence

Stored Cross-Site Scripting (XSS) vulnerability in SKT Addons for Elementor plugin allows authenticated or unauthenticated attackers to inject malicious JavaScript code through plugin input fields. The payload is stored in the database and executes when other users view affected pages in the Elementor page builder.

MitigationUpdate SKT Addons for Elementor to the latest patched version. If no update is available, implement output escaping using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) on all user-supplied input before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Skt Addons For ElementorWordPress extension

Affected:< 3.2

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify SKT Addons for Elementor is installed

Check your WordPress plugin directory for 'Skt Addons For Elementor' or 'skt-addons-for-elementor' folder under wp-content/plugins

Affected if The plugin folder exists in the plugins directory
Determine installed plugin version

Access the WordPress admin dashboard, go to Plugins > Installed Plugins, find SKT Addons for Elementor, and compare the version number to 3.2

Affected if The listed version is below 3.2 (for example, 3.1, 3.0, 2.x, etc.)
Identify active plugin widgets on pages

Search your WordPress database in wp_posts for post_content containing 'skt-addons' or review pages built with Elementor that use the SKT Addons widgets

Affected if Any pages or posts contain SKT Addons widgets or shortcodes in the content
Check for injected scripts in the database

Query wp_posts and wp_postmeta for suspicious patterns like <script, javascript:, onerror=, onload= in content associated with SKT Addons widget data

Affected if Any database entries contain encoded or raw script tags within fields that would be rendered by the plugin

If the plugin version is below 3.2 and any SKT Addons widgets are actively used on your site, the stored XSS vulnerability is present and may have been exploited.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 3.2 or later

Fixed in 3.2

Interim mitigation

Update SKT Addons for Elementor to the latest patched version. If no update is available, implement output escaping using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) on all user-supplied input before rendering.

Recommended fix Moderate confidence

Version 3.2 or later

1. Backup your WordPress site before making any changes
2. Navigate to WordPress dashboard > Plugins > Installed Plugins
3. Locate 'Skt Addons For Elementor' in the plugin list
4. Check if current version is below 3.2
5. If update available, click 'Update Now' to upgrade to version 3.2 or later
6. After update, verify the plugin is functioning correctly
7. Test the affected functionality to confirm the XSS vulnerability is remediated

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

Fix this in Skt Addons For Elementor Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38674 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-38674?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 3.2 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Skt Addons For Elementor

Remediation

Need this fixed?

Fix this in Skt Addons For Elementor 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-38674 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References