CVE-2026-22209: wpDiscuz before 7.6.47 - Cross-Site Scripting via Unescaped Custom CSS in Style Tag
wpDiscuz before 7.6.47 contains a cross-site scripting vulnerability in the customCss field that allows administrators to inject malicious scripts by breaking out of style tags. Attackers with admin access can inject payloads like </style><script>alert(1)</script> in the custom CSS setting to execute arbitrary JavaScript in user browsers.
Security readout for executives and security teams
Plain-English summary
wpDiscuz before 7.6.47 can let a WordPress administrator place JavaScript through the plugin's custom CSS setting. This is not a remote unauthenticated issue, but it can matter if admin accounts are shared, delegated, or compromised because visitors' browsers may run attacker-controlled script.
Executive priority
Treat this as a targeted maintenance and privileged-account hygiene item. It should be patched in normal WordPress update cycles, faster for public sites with many admins or recent admin-account concerns, but the sources do not support emergency prioritization.
Technical view
The vulnerability is CWE-79 stored cross-site scripting in the wpDiscuz customCss field. The field is not safely escaped inside a style tag, allowing a privileged administrator to break out of CSS context and execute JavaScript in users' browsers. CVSS is 5.5 with high privileges required and changed scope.
Likely exposure
Exposure is limited to WordPress sites running wpDiscuz versions before 7.6.47. Risk is higher where multiple administrators manage plugin settings or where privileged WordPress accounts could be compromised. The provided sources do not indicate other products are affected.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Exploitation requires administrator-level access to change the plugin's custom CSS setting, so this is mainly a privilege-abuse or post-compromise browser-impact issue rather than an initial-entry vulnerability.
Researcher notes
The key constraints are PR:H and the customCss sink inside a style tag. Assess stored XSS impact through authenticated admin configuration paths only. Do not assume unauthenticated exploitation, broader WordPress compromise, or exploitation in the wild from the supplied evidence.
Mitigation direction
Upgrade wpDiscuz to 7.6.47 or later after normal site testing.
Check vendor changelog and advisory for any additional guidance.
Review wpDiscuz custom CSS for unexpected markup or scripts.
Restrict WordPress administrator access and require MFA for privileged accounts.
Monitor plugin setting changes and unexpected frontend script behavior.
Validation and detection
Inventory WordPress sites using the wpDiscuz plugin.
Confirm installed wpDiscuz version is 7.6.47 or later.
Review who can modify wpDiscuz settings and custom CSS.
Inspect current custom CSS configuration for suspicious style-breaking content.
Check logs for recent administrator changes to plugin settings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.