# CVE-2025-54598: Cross-site request forgery in n/a

> Attackers can force users to delete all notifications via CSRF in the Bevy Event service, affecting eBay Seller Events.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-84hw-6xxj-c8x4

## What is CVE-2025-54598?

CVE-2025-54598 is a medium-severity vulnerability in n/a, published on 27 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Bevy Event service through 2025-07-22, as used for eBay Seller Events and other activities, allows CSRF to delete all notifications via the /notifications/delete/ URI.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-54598?

It affects 1 product.


Products: Bevy Bevy.

## How do I fix CVE-2025-54598?

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

## Is CVE-2025-54598 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54598 and fix it if it is affected.

What it is: CVE-2025-54598 is a medium-severity vulnerability in n/a, published on 27 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54598 exists.

Affected product: n/a. 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-2025-54598/ (Markdown: https://insights.sbomify.com/CVE-2025-54598/index.md)
```

## Sources

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

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