Live › vulnerability › CVE-2026-96870
Go to dashboardThe SureDash WordPress plugin up to and including 1.12.0 does not sanitize the display_name parameter, so a logged-in subscriber can store a script that runs in other users' browsers. The script runs when a user hovers over a comment's like counter on a community page, which lets an attacker act as the victim on the site.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the SureDash community and member dashboard plugin at version 1.12.0 or earlier are exposed. The risk depends on users being able to register or hold subscriber accounts, since those accounts are what let an attacker store the payload; sites where only administrators can log in are lower risk.
No product ranges from the sources yet.
wp plugin get suredash --field=version1.12.0; the exact fixed version is unknown from the sourcesEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
The SureDash – Community, Courses & Member Dashboard plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name' parameter in all versions up to, and including, 1.12.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit is triggered when any user hovers over a comment's like counter on a community page, as the plugin's tooltip handler assigns the attacker-controlled data-tooltip-description attribute value directly to innerHTML, re-parsing the browser-decoded entity payload as live HTML.
This page as .md · .json · in your agent: get_signal("CVE-2026-96870")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.