CVE-2026-6646
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 · uneditedThe The7 theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'dt_default_button' shortcode in all versions up to, and including, 14.3.2. This is due to insufficient input sanitization and output escaping on the 'title' component of the 'link' shortcode parameter. 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 confidenceThe The7 WordPress theme fails to sanitize and escape the 'title' attribute within the 'dt_default_button' shortcode's 'link' parameter, allowing authenticated users with Contributor-level access to inject malicious JavaScript that persists in the database and executes when other users view affected pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm The7 theme is installedNavigate to wp-content/themes/ in your WordPress installation directory and verify the 'the7' theme folder existsAffected if The the7 folder is present in the themes directory
-
Check The7 theme versionIn WordPress admin, go to Appearance > Themes and click on The7 to view the theme version, or inspect the style.css file within the theme folder for the 'Version:' headerAffected if The installed version is lower than 14.3.3 (the patched release)
-
Identify dt_default_button shortcode usageSearch your WordPress database for instances of the shortcode: SELECT * FROM wp_posts WHERE post_content LIKE '%dt_default_button%' (adjust prefix if custom)Affected if Any posts or pages contain the dt_default_button shortcode with a 'link' parameter that includes a 'title' attribute
-
Verify Contributor-level user accessCheck user roles in WordPress admin under Users > All Users to confirm accounts with Contributor role exist and have shortcode usage capabilityAffected if Contributor-level or higher users can create or edit content containing the vulnerable shortcode
-
Inspect for suspicious title attributesExamine the 'link' parameter values in dt_default_button shortcodes found in post content, looking for encoded or obfuscated script tags in the title attributeAffected if The title attribute contains JavaScript code, encoded characters like <script>, or unusual URL-encoded sequences
Your environment is affected if The7 theme is installed with a version below 14.3.3 and content containing the dt_default_button shortcode with a crafted title attribute exists in the database, especially when Contributor-level users can create or edit such 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.
From vendor dataUpdate The7 theme to version 14.3.3 or later once available. In the interim, restrict shortcode usage permissions to Administrators only and implement Content Security Policy headers to mitigate XSS execution.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6646 — 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-2026-6646 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