Skt BlocksWordPress extension · Sktthemes
CVE-2024-43946
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in SKT Themes SKT Blocks – Gutenberg based Page Builder allows Stored XSS.This issue affects SKT Blocks – Gutenberg based Page Builder: from n/a through 1.5.
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 confidenceStored XSS vulnerability in SKT Blocks WordPress plugin allows malicious scripts to be injected through plugin inputs and persisted in the database, executing when other users view the affected content. The issue stems from improper input sanitization during web page generation.
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 BlocksWordPress extension
<= 1.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SKT Blocks plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Skt Blocks' or 'SKT Blocks' in the plugin list. Note the installed version number displayed below the plugin name.Affected if Plugin is present with version 1.5 or lower
-
Identify plugin input handling pointsInspect the plugin directory (wp-content/plugins/skt-blocks) for PHP files that process user input. Look for form handlers, shortcode callbacks, or block editor integrations that accept user-submitted data.Affected if Plugin processes any user-supplied input through its forms, blocks, or shortcodes
-
Search database for suspicious stored contentQuery the WordPress database (wp_posts table) for script tags or javascript: URIs in post_content, using: SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%javascript:%';Affected if Any posts contain unsanitized script tags or event handlers (onerror, onload, etc.) injected through plugin inputs
-
Review recent admin-created contentCheck posts/pages created or edited by administrators for unexpected HTML/script content, particularly in areas where SKT Blocks components were used. Inspect the HTML source of published pages.Affected if Published content displays JavaScript code that was not intentionally added by administrators
User is affected if SKT Blocks plugin version 1.5 or lower is installed AND the plugin is actively used to render or process user-accessible content where input is not sanitized before storage.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor patch when available; until then, implement proper sanitization (sanitize_text_field, esc_html, esc_attr) on all user inputs before storage and escaping on output in the affected plugin code.
Latest version of SKT Blocks after 1.5 (contact vendor for exact version number)
- Check WordPress plugin repository or contact SKT Themes directly to obtain the latest version of SKT Blocks that includes the security fix for CVE-2024-43946
- Update SKT Blocks plugin to the latest available version via WordPress admin dashboard or FTP
- After updating, verify the plugin version in WordPress admin under Plugins > Installed Plugins
- Clear any site caches if caching plugins are in use
- Test that the Gutenberg block builder functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Skt Blocks
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-43946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43946 in production — separate from our analysis above.
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.
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.
- 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