RTMKit <= 2.0.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via Advanced Heading Widget 'Background Text' Parameter
The RTMKit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Advanced Heading widget's 'Background Text' parameter in versions up to, and including, 2.0.7 This is due to insufficient output escaping on the 'background_text_heading' setting in the render() function, which concatenates the value directly into an HTML attribute without applying esc_attr(). 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.
Quick answer
RTMKit should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-2.0.7
Fixed versions
- 2.0.8
How to fix it
RTMKit is affected by CVE-2026-8351, a stored cross-site scripting issue in versions *-2.0.7. Prioritize sites where contributor, author, editor, vendor, or customer-submitted content can reach public pages. The recommended remediation is to update to version 2.0.8 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable workflow, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses RTMKit, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with versions *-2.0.7 from the linked advisory.
- Apply the remediation: update to version 2.0.8 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable RTMKit, remove unused roles that can reach the vulnerable feature, and restrict the affected admin, REST, shortcode, upload, booking, ecommerce, review, or content workflow.
- Review application, web server, security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-8351.
- Rotate administrator sessions, API keys, webhook secrets, database credentials, and integration tokens if logs or file/content review suggest compromise.
- Clear application, object, page, CDN, and browser caches after remediation so vulnerable assets, stored payloads, or stale responses are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm RTMKit is no longer running versions *-2.0.7 and record the patched or mitigated version in the remediation ticket.
- Verify unauthenticated, subscriber, contributor, author, editor, shop manager, booking, vendor, or custom-role users can no longer trigger the affected action.
- Review logs before and after the fix for exploitation attempts, unexpected content changes, suspicious admin actions, or database/file access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory link, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-8351?
RTMKit versions listed as affected should be reviewed: *-2.0.7.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.