dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-5748

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Text Snippets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `ts` shortcode in all versions up to, and including, 0.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Text Snippets WordPress plugin suffers from a stored XSS vulnerability in the `ts` shortcode. The plugin fails to properly sanitize and escape user-supplied attributes before outputting them, allowing authenticated users with contributor-level or higher permissions to inject arbitrary JavaScript that executes when other users view the affected pages.

MitigationUpdate the plugin to a patched version once available. Until then, remove or disable the Text Snippets plugin, or restrict user creation/shortcode usage to trusted administrators only.

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

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify Text Snippets plugin is installed
    Go to WordPress admin > Plugins and look for 'Text Snippets' in the installed plugins list
    Affected if The plugin is installed and active
  2. Check the installed version of Text Snippets
    In Plugins list, click on the plugin name to view version details, or inspect plugin header in wp-content/plugins/text-snippets/text-snippets.php
    Affected if Version cannot be determined or is earlier than the patched version (compare against release notes when available)
  3. Identify usage of the ts shortcode
    Search WordPress database or use a plugin scanner to find instances of [ts] shortcode in posts, pages, or widgets: SELECT * FROM wp_posts WHERE post_content LIKE '%[ts %'
    Affected if The [ts] shortcode is present in any published content
  4. Review user accounts with contributor-level or higher roles
    Go to WordPress admin > Users and examine roles; contributors, authors, editors, and administrators have the capability to use shortcodes
    Affected if Any user account has contributor-level or higher permission

A user is affected if the Text Snippets plugin is active, the ts shortcode is used in content, and any authenticated user with contributor-level or higher access exists in the system.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version once available. Until then, remove or disable the Text Snippets plugin, or restrict user creation/shortcode usage to trusted administrators only.

Recommended fix Moderate confidence

latest version beyond 0.0.1 (verify exact version number at wordpress.org/plugins/text-snippets or plugins.trac.wordpress.org)

  1. Check the WordPress admin dashboard for plugin updates under Plugins > All Plugins
  2. Update the Text Snippets plugin to the latest available version
  3. If automatic updates are not available, manually download the latest version from the WordPress Plugin Repository at plugins.trac.wordpress.org
  4. After updating, verify the fix by ensuring the `ts` shortcode properly sanitizes and escapes user-supplied attributes
  5. Confirm that contributor-level users can no longer inject arbitrary scripts through shortcode attributes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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