Live › vulnerability › CVE-2026-111068
Go to dashboardThe DesignSetGo WordPress plugin up to and including 2.11.0 does not sanitize the 'tagName' parameter, so a contributor can store a script that is saved into page content during the plugin's block-conversion migration. When a user opens the injected page, the script runs in their browser.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running DesignSetGo 2.11.0 or earlier where contributors can create content. Exploitation also requires an administrator to run the plugin's block-conversion migration during deactivation, so sites without contributor accounts or without that migration are less exposed. Sites that have already updated or removed the plugin can skip it.
No product ranges from the sources yet.
wp plugin get designsetgo --field=version2.11.0 (the patched version is unknown from the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The DesignSetGo plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tagName' parameter in all versions up to, and including, 2.11.0 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. Successful exploitation requires an administrator to run the plugin's block-conversion migration ("Scan & Convert Blocks" during deactivation), which triggers the vulnerable build_group_block() function and promotes the dormant payload from a block delimiter comment into live post_content HTML. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
This page as .md · .json · in your agent: get_signal("CVE-2026-111068")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.