Skt BlocksWordPress extension · Sktthemes
CVE-2025-46235
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 ('Cross-site Scripting') vulnerability in sonalsinha21 SKT Blocks skt-blocks allows Stored XSS.This issue affects SKT Blocks: from n/a through <= 2.0.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the SKT Blocks plugin where user-supplied input within blocks is not properly sanitized before being rendered in web pages, allowing malicious scripts to be persisted and executed when users view infected content.
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
< 2.1CVSS 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 installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'Sktthemes Skt Blocks' or 'SKT Blocks' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'skt-blocks' or similar.Affected if The plugin is installed and active on the WordPress site
-
Identify installed version numberIn WordPress admin, go to Plugins > Installed Plugins > SKT Blocks and look for the version number displayed. Alternatively, check the main plugin PHP file for a 'Version' header comment, or look at the plugin folder for a readme.txt or composer.json file containing version info.Affected if The version number is below 2.1 (e.g., 2.0, 1.9, etc.)
-
Check for user-created blocks with custom contentNavigate to the WordPress block editor (Gutenberg) or check pages/posts where SKT Blocks were used. Look for blocks that accept user input such as text fields, heading fields, button text, or custom HTML blocks.Affected if SKT Blocks with editable user fields exist in the content
-
Inspect stored block content for potential XSS payloadsAccess the WordPress database via phpMyAdmin or wp-cli. Query the wp_posts table for posts containing SKT Blocks markup (look for '<!-- wp:skt-blocks' or similar block comments) and examine the content for suspicious patterns like <script> tags, javascript: URLs, or event handlers (onclick, onerror, etc.).Affected if Any stored content contains unsanitized HTML/JavaScript that could execute in a browser
If SKT Blocks version is below 2.1 and the site contains blocks with user-editable content that may not have been sanitized, the installation is likely affected by this stored XSS vulnerability.
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.
From vendor data2.1
Update SKT Blocks to the latest patched version when released, or implement proper input sanitization and output escaping on all user-controlled fields within the plugin blocks.
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-2025-46235 — 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-2025-46235 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