Skt BlocksWordPress extension · Sktthemes
CVE-2025-26998
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 <= 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 confidenceThis is a stored Cross-site Scripting (XSS) vulnerability in the SKT Blocks WordPress plugin. The vulnerability allows malicious JavaScript to be injected through unsanitized user input that gets stored on the server and executed when other users view affected pages. The issue affects all versions of skt-blocks up to and including version 1.8.
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.9CVSS 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 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'.Affected if The plugin is present in the WordPress installation
-
Identify the installed version numberIn the WordPress plugins list, click on the plugin to view details and find the version number. Or open the main plugin file (usually skt-blocks.php) and look for the 'Version:' header comment at the top of the file.Affected if The version is 1.8 or lower (any version below 1.9)
-
Verify if the plugin has any user input functionalityAccess the SKT Blocks settings page in the WordPress admin. Look for any blocks, widgets, or settings that accept user-supplied text, URLs, or HTML content. Check the Gutenberg block editor if SKT Blocks provides custom blocks that accept user input.Affected if The plugin contains blocks or settings that accept and store user-supplied text or HTML content
-
Inspect stored content for unsanitized outputCreate a new post or page using an SKT Blocks custom block that accepts user input. Enter a test string containing HTML characters (e.g., '<script>alert(1)</script>') and publish. View the published page source to see if the characters are rendered as-is without encoding.Affected if User-supplied content containing HTML is rendered without proper escaping (the script tags appear literally in the page source rather than being encoded)
A user is affected if the SKT Blocks plugin version is 1.8 or lower AND the plugin is actively used with blocks or settings that accept and display user input content.
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 · scoped1.9
Update skt-blocks to the latest patched version once available. If no patch exists, implement proper input sanitization (sanitize_text_field, wp_kses_post) on all user inputs and output encoding (esc_html, esc_attr, wp_kses) before rendering user-supplied content in HTML contexts.
Skt Blocks version 1.9
- 1. Back up your WordPress site and database before performing any updates.
- 2. Navigate to the WordPress admin dashboard.
- 3. Go to Plugins > Installed Plugins.
- 4. Find "Skt Blocks" in the plugin list.
- 5. If an update is available, click "Update Now" to update to version 1.9.
- 6. Alternatively, download Skt Blocks version 1.9 from a trusted source and upload it via Plugins > Add New > Upload Plugin.
- 7. After updating, verify the plugin is running version 1.9 under Plugins > Installed Plugins.
- 8. 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 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-26998 — 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-26998 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