# PowSyBl Core XML Reader allows XXE and SSRF

Advisory record · `GHSA-qpj9-qcwx-8jv2`

- **Identifiers:** `GHSA-qpj9-qcwx-8jv2` · `CVE-2025-47293`
- **State:** Confirmed
- **Severity:** CVSS 2.7 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-611](https://cwe.mitre.org/data/definitions/611.html) · [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md) · [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 19 Jun 2025
- **Updated:** 20 Jun 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Jun 2025, 14:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.powsybl:powsybl-commons` (Maven): affected `<6.7.2`; fixed in `6.7.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> PowSyBl Core's com.powsybl:powsybl-commons package, versions before 6.7.2, has XML external entity (XXE) and server-side request forgery (SSRF) flaws in its XML reader. An attacker who can submit XML to affected methods, such as by importing network files in a multi-tenant application, could read files they lack permission to access, including sensitive system files. Upgrade to powsybl-commons 6.7.2 or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.7 Low, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0044, the 38th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qpj9-qcwx-8jv2)

## Sources

- [GitHub Advisory Database: GHSA-qpj9-qcwx-8jv2](https://github.com/advisories/GHSA-qpj9-qcwx-8jv2)
- [OSV: GHSA-qpj9-qcwx-8jv2](https://osv.dev/vulnerability/GHSA-qpj9-qcwx-8jv2)
- <https://github.com/powsybl/powsybl-core/security/advisories/GHSA-qpj9-qcwx-8jv2>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-47293>
- <https://github.com/powsybl/powsybl-core/commit/e6c7c4997ae8758b54a2f23ce1a499e25113acdc>
- <https://github.com/powsybl/powsybl-core>
- <https://github.com/powsybl/powsybl-core/releases/tag/v6.7.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qpj9-qcwx-8jv2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qpj9-qcwx-8jv2/>. Everything for agents: <https://agentprime.io/llms.txt>.