CVE-2026-8841
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 Extra Settings for RocketChat plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'rocketchat' shortcode's 'title' attribute in versions up to, and including, 0.1. This is due to insufficient input sanitization and output escaping in the rxstg_shortcode() function, which concatenates the user-supplied 'title' attribute directly into HTML output. 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 Extra Settings for RocketChat WordPress plugin (versions up to 0.1) contains a stored XSS vulnerability in the rxstg_shortcode() function. The 'title' attribute of the 'rocketchat' shortcode is not sanitized before being output, allowing authenticated contributors+ to inject malicious JavaScript that executes when 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 plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'Extra Settings for RocketChat'. Note the version number displayed. Compare against any known affected version range.Affected if The plugin is installed and its version falls within the affected range (if known) or is of unknown/older version without the fix.
-
Identify shortcode usageSearch your WordPress database for posts/pages containing the shortcode '[rocketchat]' by querying the wp_posts table or using a plugin that scans for shortcodes.Affected if The shortcode [rocketchat] is present in any published content.
-
Inspect shortcode for title parameter usageExamine the content of posts/pages using the [rocketchat] shortcode to see if the 'title' attribute is being used (e.g., [rocketchat title="somevalue"]).Affected if The shortcode is used with a 'title' attribute.
-
Review the shortcode handler codeAccess the plugin files via FTP or file manager. Locate the file containing the rxstg_shortcode function and inspect whether it uses sanitize_text_field, esc_html, or esc_attr on the title parameter before outputting it.Affected if The title attribute is not sanitized with functions like sanitize_text_field and not escaped with esc_html or esc_attr in the shortcode handler.
A user is affected if the Extra Settings for RocketChat plugin is installed, the [rocketchat] shortcode with a 'title' attribute is in use, and the shortcode handler does not properly sanitize or escape the title parameter.
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 of the plugin that implements proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html or esc_attr) on the title attribute before HTML concatenation.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8841 — 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-8841 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