CVE-2026-8870
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 Team Master – A Modern WordPress Team Showcase plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Shortcode Attributes in all versions up to, and including, 1.1.2 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 Team Master WordPress plugin fails to sanitize shortcode attributes before outputting them, allowing stored XSS. Attackers with contributor-level access can inject malicious JavaScript via shortcode parameters that executes whenever pages containing the shortcode are accessed.
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 Team Master plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Team Master' or check wp-content/plugins/ for a folder named 'team-master' or similar. Retrieve the installed version number from the plugin header.Affected if The plugin is installed and active.
-
Identify active shortcode usageSearch your WordPress pages, posts, and widgets for the Team Master shortcode (commonly [team_master] or similar) by searching the wp_posts table or using a plugin that lists all shortcodes.Affected if The shortcode is present in any published content.
-
Verify contributor-level user accounts existNavigate to Users > All Users in WordPress admin and check for users with the 'Contributor' role, or query the wp_users and wp_usermeta tables to identify users where meta_value contains 'contributor'.Affected if At least one contributor-level user account exists.
-
Inspect shortcode output for XSS vulnerabilitiesView the source of a page containing the shortcode and check if shortcode attributes (such as name, title, role, or any parameters) are properly escaped. Look for unescaped output - the raw attribute values should be escaped with esc_html(), esc_attr(), or similar functions in the plugin code.Affected if Shortcode attributes appear unescaped in the HTML output (raw user-supplied values visible without HTML encoding).
You are affected if the Team Master plugin is installed, the shortcode is in use, and the output shows unescaped shortcode attributes that could contain malicious scripts.
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 the plugin to the latest version when available, or implement proper input sanitization (e.g., esc_attr()) and output escaping (e.g., esc_html(), wp_kses()) on all shortcode attribute values before rendering.
- 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-8870 — 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-8870 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