CVE-2026-10024
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 TinyMCE shortcode Addon plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'btnrel' Shortcode Attribute in all versions up to, and including, 1.0.0 due to insufficient input sanitization and output escaping. 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 TinyMCE shortcode Addon plugin for WordPress up to version 1.0.0 contains a stored XSS vulnerability in the 'btnrel' shortcode attribute. Authenticated attackers with contributor-level access can inject arbitrary JavaScript via the shortcode because the plugin fails to properly sanitize input and escape output.
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.
-
Identify plugin installation and versionCheck the WordPress plugins directory for the TinyMCE shortcode Addon folder and read the main plugin file header to obtain the installed version numberAffected if The plugin is installed and the version is lower than 1.0.1 (or version cannot be determined)
-
Confirm vulnerable shortcode is in useSearch WordPress post content (wp_posts table) or page editor for shortcode usage containing the btnrel attribute, such as [tinymce_button btnrel="value"] or similar TinyMCE shortcode variantsAffected if Pages or posts contain shortcodes that include the btnrel attribute without manual escaping
-
Inspect rendered output for XSS vulnerabilityView a page containing the vulnerable shortcode in a browser, right-click and inspect the HTML element corresponding to the button/element that uses the btnrel attribute, then check if the btnrel value appears unescaped in the HTML (e.g., quotes are not " or the value contains raw user-supplied content)Affected if The btnrel attribute value appears in the rendered HTML without proper escaping (not using esc_attr or equivalent)
-
Review plugin source for sanitizationIf plugin files are accessible, open the main plugin PHP file and search for the shortcode handler function to verify if sanitize_text_field is applied to the btnrel attribute input and esc_attr is used on outputAffected if The btnrel attribute is not sanitized with sanitize_text_field and not escaped with esc_attr in the output code
A user is affected if the TinyMCE shortcode Addon plugin is installed with a version below 1.0.1 AND pages containing the btnrel shortcode attribute are accessible to authenticated users who can inject the payload.
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 to a patched version if available; otherwise disable the plugin. Audit existing content for malicious btnrel shortcode usage and remove any injected scripts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10024 — 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-10024 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