dbcve.org
Skt BlocksWordPress extension · Sktthemes

CVE-2025-26771

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-17
Fix available
A fix is available. Upgrade to 1.8 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 sonalsinha21 SKT Blocks skt-blocks allows Stored XSS.This issue affects SKT Blocks: from n/a through <= 1.7.

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 confidence

Stored cross-site scripting (XSS) vulnerability in the SKT Blocks WordPress plugin allows attackers to inject malicious JavaScript code through plugin blocks that is stored in the database and executed when other users view affected pages. The vulnerability stems from improper input sanitization and output encoding of user-supplied data.

MitigationUpdate SKT Blocks to the latest version which includes proper input sanitization and output escaping. Until then, restrict usage of SKT Blocks to trusted users only and implement Content Security Policy headers as defense-in-depth.

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
Affected:< 1.8

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. Confirm SKT Blocks plugin is installed
    Navigate to WordPress admin > Plugins and look for 'SKT Blocks' or 'Skt Blocks' in the installed plugins list
    Affected if Plugin is present in the WordPress installation
  2. Identify installed version
    In Plugins list, click on the plugin to view details, or check the plugin header in /wp-content/plugins/skt-blocks/ directory for the Version field
    Affected if Version number is less than 1.8 or version cannot be determined ( Treat as vulnerable )
  3. Verify blocks are in use on the site
    Check pages/posts for SKT Blocks by viewing page source or using a database query: SELECT * FROM wp_posts WHERE post_content LIKE '%skt-blocks%' OR post_content LIKE '%<!-- wp:skt-blocks%'
    Affected if Any SKT Blocks are present in published content
  4. Check for malicious script patterns in block content
    Review the block content in the database: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onload=%' OR post_content LIKE '%onerror=%'
    Affected if Suspicious JavaScript tags or event handlers are found in content containing SKT Blocks

If SKT Blocks version is below 1.8 AND the plugin is actively used on the site, the installation is vulnerable to stored XSS via this 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.8 or later
Fixed in 1.8
Interim mitigation

Update SKT Blocks to the latest version which includes proper input sanitization and output escaping. Until then, restrict usage of SKT Blocks to trusted users only and implement Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

SKT Blocks version 1.8

  1. Create a full backup of your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate SKT Blocks in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.8
  5. After updating, clear any caching mechanisms (site cache, CDN cache, browser cache)
  6. Verify the plugin shows version 1.8 as installed

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
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-2025-26771 — 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-2025-26771 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