CVE-2026-7623 is a stored Cross-Site Scripting vulnerability in the SureForms WordPress plugin through version 2.8.1. An authenticated Contributor or a user with higher privileges can place a crafted headingWrapper attribute in the Advanced Heading block. When WordPress renders the saved block, the value can introduce a JavaScript event handler into the page and execute code in another user’s browser. The issue is fixed in version 2.8.2.
| CVE | CVE-2026-7623 |
| Plugin Version | SureForms <= 2.8.1, fixed in 2.8.2 |
| All Time | 6 111 128 |
| Active installations | 500 000+ |
| Publicly Published | February 28, 2026 |
| Last Updated | February 28, 2026 |
| Researcher | Dmitrii Ignatyev |
| CWE | CWE-79 Cross-Site Scripting |
| PoC | Yes |
| Exploit | No |
| Reference | https://www.cve.org/CVERecord?id=CVE-2026-7623 https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/sureforms/sureforms-281-authenticated-contributor-stored-cross-site-scripting-via-headingwrapper-block-attribute |
| Plugin Security Certification by CleanTalk | ![]() |
| Logo of the plugin | ![]() |
PSC by CleantalkJoin the community of developers who prioritize security. Highlight your plugin in the WordPress catalog.
Timeline
| February 28, 2026 | Plugin testing and vulnerability detection in SureForms were completed. |
| February 28, 2026 | The vulnerability report was sent with the PoC, description, and recommendations for remediation. |
| February 28, 2026 | Publication date assigned to this research article about CVE-2026-7623. |
Discovery of the Vulnerability
The affected server-side block is registered as srfm/advanced-heading. In the SureForms 2.8.1 rendering callback, render_html() reads headingWrapper from the saved block attributes and assigns the supplied value to $element. The renderer places that value immediately after the opening angle bracket of the wrapper element. The attribute therefore controls an HTML tag-name position.
The output uses esc_attr(), but attribute escaping does not validate an element name. A value such as img src=x onerror=alert(document.domain) contains spaces and an event handler without needing quotation marks. In this position it becomes an image tag with additional attributes. Filtering the heading text with wp_kses() does not protect the separately constructed outer wrapper.
Understanding of Stored Cross-Site Scripting attacks
Stored Cross-Site Scripting occurs when attacker-controlled data survives saving and is later rendered as executable browser content. Here, the payload resides in a Gutenberg block attribute rather than in the visible heading text. Reviewing only the text of a post can miss the value that changes the surrounding HTML.
The attacker needs a Contributor account or higher. Contributors normally submit content for review, so exploitation can affect an editor who previews a submitted draft. Public visitors can be exposed if a user with publishing permission publishes the affected content. JavaScript runs in the site origin and can act within the capabilities of the viewing browser session.
Exploiting the Stored Cross-Site Scripting Vulnerability
The following non-destructive reproduction is derived from the affected rendering code. It uses a domain alert as a marker and describes the expected vulnerable and patched behavior. Use an isolated WordPress test installation with SureForms 2.8.1 active.
POC:
POC: Account - Contributor or higher Affected plugin - SureForms 2.8.1 Method - source-based reproduction on an isolated test site 1. Sign in to the test site as a Contributor and create a new post. 2. Switch the WordPress block editor to Code editor. 3. Insert the following serialized block. <!-- wp:srfm/advanced-heading {"block_id":"heading-security-review","headingWrapper":"img src=x onerror=alert(document.domain)","headingTitle":"Heading security review","headingTag":"h2","headingTitleToggle":true,"headingDescToggle":false,"headingDescPosition":"below-heading","separatorStyle":"none","separatorPosition":"below-heading"} /--> 4. Save the draft and reopen it to confirm the block attributes persist. 5. Preview the saved draft as a user permitted to view it. A Contributor cannot publish independently. An Editor can also publish it in the lab. 6. On an affected site, the wrapper becomes an image element whose onerror handler is expected to display alert(document.domain). 7. Update to 2.8.2 or a newer patched release and render the same saved block again. The wrapper should fall back to div and no alert should run.____
The alert demonstrates browser-side execution only. This source-based walkthrough does not claim a separate live reproduction. On sites that enforce a Content Security Policy blocking inline event handlers, the browser may suppress the alert even while the unsafe wrapper is present.
Recommendations for Improved Security
Update SureForms to 2.8.2 or a newer patched release, preferably the latest supported version. Review pending and recently published content from lower privileged accounts for unusual srfm/advanced-heading attributes. Remove injected values from saved content and keep publishing permissions limited to accounts that need them.
Developers should validate tag-name attributes against a strict allowlist before rendering. The 2.8.2 callback accepts only div and header for the wrapper, falling back to div for other values. It also restricts the heading tag to supported elements. Retain context-appropriate escaping for normal attributes and URLs, and test server-side rendering with blocks submitted by accounts without unfiltered_html.
Restricting the Advanced Heading wrapper to known tag names closes the rendering path behind CVE-2026-7623. Keeping SureForms updated protects readers and editors who view content created by less privileged accounts.
#WordPressSecurity #StoredXSS #SureForms #PluginSecurity #WebsiteSafety #StayProtected
Use CleanTalk solutions to improve the security of your website.

