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

> Attackers can perform cross-site request forgery against Fanvil x7a IP phones due to missing cross-origin resource protection on state-changing requests.

- **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:** 7 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-mqgg-wf4q-w7jv

## What is CVE-2025-70522?

CVE-2025-70522 is a high-severity vulnerability in n/a, published on 7 Oct 2026. 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 request handler of Fanvil x7a firmware version 2.6.0.1182 does not enforce any cross-origin resource protection for any state-changing request performed against the applications. Due to the lack of protection, cross-origin boundary can be completely bypassed, allowing for Cross-Site Request Forgery Attacks against any endpoint.

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

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


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

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

## Is CVE-2025-70522 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70522 is a high-severity vulnerability in n/a, published on 7 Oct 2026. 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-70522 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-70522/ (Markdown: https://insights.sbomify.com/CVE-2025-70522/index.md)
```

## Sources

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

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