# CVE-2023-24403: WordPress bbPress Voting Plugin <= 2.1.11.0 is vulnerable to Cross-Site Scripting (XSS)

> An authenticated admin can inject malicious scripts into the bbPress Voting plugin, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-g4rm-24j6-m53h

## What is CVE-2023-24403?

CVE-2023-24403 is a medium-severity cross-site scripting vulnerability in WP For The Win bbPress Voting, published on 6 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in WP For The Win bbPress Voting plugin <= 2.1.11.0 versions.

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

## Which versions are affected by CVE-2023-24403?

It affects 1 product.


Products: Wpforthewin Bbpress Voting.

## How do I fix CVE-2023-24403?

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

## Is CVE-2023-24403 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24403 and fix it if it is affected.

What it is: CVE-2023-24403 is a medium-severity cross-site scripting vulnerability in WP For The Win bbPress Voting, published on 6 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-24403 in the wild and no public exploit code.

Affected product: WP For The Win bbPress Voting. 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-2023-24403/ (Markdown: https://insights.sbomify.com/CVE-2023-24403/index.md)
```

## Sources

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

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