# CVE-2023-5140: Bonus for Woo < 5.8.3 - Reflected Cross-Site Scripting

> Reflected XSS in Bonus for Woo plugin allows attackers to execute scripts against admin users, potentially leading to account takeover.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8xvx-w4v2-926g

## What is CVE-2023-5140?

CVE-2023-5140 is a medium-severity cross-site scripting vulnerability in Unknown Bonus for Woo, published on 20 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Bonus for Woo WordPress plugin before 5.8.3 does not sanitise and escape some parameters before outputting them back in pages, leading to Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

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

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

It affects 1 product.


Products: Computy Bonus for Woo.

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

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

## Is CVE-2023-5140 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5140 is a medium-severity cross-site scripting vulnerability in Unknown Bonus for Woo, published on 20 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-5140 in the wild and no public exploit code.

Affected product: Unknown Bonus for Woo. 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-5140/ (Markdown: https://insights.sbomify.com/CVE-2023-5140/index.md)
```

## Sources

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

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