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

> A CSRF vulnerability in AllSky allows remote attackers to cause a denial of service via the handle_interface_POST_and_status function.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 9 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-88wg-48f3-4qgx

## What is CVE-2025-65573?

CVE-2025-65573 is a high-severity vulnerability in n/a, published on 9 Dec 2025. 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

Cross Site Request Forgery (CSRF) vulnerability in AllskyTeam AllSky v2024.12.06_06 allows remote attackers to cause a denial of service via function handle_interface_POST_and_status.

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

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

It affects 1 product.


Products: Allskyteam Allsky.

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

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

## Is CVE-2025-65573 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63414](https://insights.sbomify.com/CVE-2025-63414/): Command injection in n/a (critical 10.0)
- [CVE-2025-65572](https://insights.sbomify.com/CVE-2025-65572/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65573 is a high-severity vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, 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-2025-65573 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-65573/ (Markdown: https://insights.sbomify.com/CVE-2025-65573/index.md)
```

## Sources

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

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