# CVE-2025-64252: WordPress ANAC XML Viewer plugin <= 1.8.2 - Server Side Request Forgery (SSRF) vulnerability

> An attacker can exploit a Server-Side Request Forgery vulnerability in the ANAC XML Viewer plugin to make the server send requests to arbitrary destinations.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-rpvq-43pv-vpgx

## What is CVE-2025-64252?

CVE-2025-64252 is a medium-severity server-side request forgery vulnerability in Marco Milesi ANAC XML Viewer, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in Marco Milesi ANAC XML Viewer anac-xml-viewer allows Server Side Request Forgery.This issue affects ANAC XML Viewer: from n/a through <= 1.8.2.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2025-64252 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64252 is a medium-severity server-side request forgery vulnerability in Marco Milesi ANAC XML Viewer, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64252 in the wild and no public exploit code.

Affected product: Marco Milesi ANAC XML Viewer. 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-64252/ (Markdown: https://insights.sbomify.com/CVE-2025-64252/index.md)
```

## Sources

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

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