# CVE-2022-3909: Add Comments <= 1.0.1 - Admin+ Stored XSS

> Admin users can inject malicious scripts via unsanitized settings in the Add Comments plugin, affecting multisite environments.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-3h6h-wq56-3w89

## What is CVE-2022-3909?

CVE-2022-3909 is a medium-severity cross-site scripting vulnerability in Unknown Add Comments, published on 5 Dec 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Add Comments WordPress plugin through 1.0.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

## Which versions are affected by CVE-2022-3909?

It affects 1 product.


Products: Add Comments Project Add Comments.

## How do I fix CVE-2022-3909?

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

## Is CVE-2022-3909 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3909 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3909 and fix it if it is affected.

What it is: CVE-2022-3909 is a medium-severity cross-site scripting vulnerability in Unknown Add Comments, published on 5 Dec 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3909 exists.

Affected product: Unknown Add Comments. 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-2022-3909/ (Markdown: https://insights.sbomify.com/CVE-2022-3909/index.md)
```

## Sources

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

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