# CVE-2023-24499: Butterfly Button plugin may leave traces of its use on user's device

> The Butterfly Button plugin leaves traces on the user's device, potentially disclosing sensitive usage information to unauthorized parties like spouses.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-69ch-324r-wxh6

## What is CVE-2023-24499?

CVE-2023-24499 is a medium-severity vulnerability in Butterfly Button plugin, published on 15 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Butterfly Button plugin may leave traces of its use on user's device. Since it is used for reporting domestic problems, this may lead to spouse knowing about its use.

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

It affects 1 product.


Products: Butterfly-Button Project Butterfly-Button.

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

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

## Is CVE-2023-24499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-24499 is a medium-severity vulnerability in Butterfly Button plugin, published on 15 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-24499 in the wild and no public exploit code.

Affected product: Butterfly Button plugin. 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-24499/ (Markdown: https://insights.sbomify.com/CVE-2023-24499/index.md)
```

## Sources

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

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