# CVE-2026-22209: wpDiscuz before 7.6.47 - Cross-Site Scripting via Unescaped Custom CSS in Style Tag

> Administrators can inject malicious JavaScript via unescaped custom CSS in wpDiscuz, leading to arbitrary script execution in user browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-hrwg-p9c4-49wp

## What is CVE-2026-22209?

CVE-2026-22209 is a medium-severity cross-site scripting vulnerability in gVectors wpDiscuz, published on 13 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-22209?

It affects 1 product.


Products: Gvectors Wpdiscuz.

## How do I fix CVE-2026-22209?

No fix has been published for CVE-2026-22209 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22209 being exploited?

There is no known exploitation of CVE-2026-22209 in the wild and no public exploit code.

## Other vulnerabilities in gVectors wpDiscuz

- [CVE-2020-24186](https://insights.sbomify.com/CVE-2020-24186/): File upload in n/a (critical 10.0)
- [CVE-2024-9488](https://insights.sbomify.com/CVE-2024-9488/): Comments – wpDiscuz <= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider (critical 9.8)
- [CVE-2020-13640](https://insights.sbomify.com/CVE-2020-13640/): SQL injection in n/a (critical 9.8)
- [CVE-2026-22193](https://insights.sbomify.com/CVE-2026-22193/): wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions() (critical 9.2)
- [CVE-2026-22192](https://insights.sbomify.com/CVE-2026-22192/): Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22209 and fix it if it is affected.

What it is: CVE-2026-22209 is a medium-severity cross-site scripting vulnerability in gVectors wpDiscuz, published on 13 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22209 in the wild and no public exploit code.

Affected product: gVectors wpDiscuz. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22209/ (Markdown: https://insights.sbomify.com/CVE-2026-22209/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22209
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22209
- OSV: https://osv.dev/vulnerability/CVE-2026-22209

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22209/
Summaries are generated and may contain mistakes; the official description above is the record.