Summary
PowSyBl Core XML Reader allows XXE and SSRF
Am I impacted?
You are vulnerable if you allow untrusted users to import untrusted CGMES or XIIDM network files.
References
Impact
What kind of vulnerability is it? Who is impacted?
In certain places, powsybl-core XML parsing is vulnerable to an XXE attack and in on place also to an SSRF attack.
This allows an attacker to elevate their privileges to read files that they do not have permissions to, including sensitive files on the system.
The vulnerable class is com.powsybl.commons.xml.XmlReader which is considered to be untrusted in use cases where untrusted users can submit their XML to the vulnerable methods. This can be a multi-tenant application that hosts many different users perhaps with different privilege levels.
An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
com.powsybl:powsybl-commons:6.7.2 and higher
Frequently Asked Questions
- What is CVE-2025-47293? CVE-2025-47293 is a low-severity XML external entity injection (XXE) vulnerability in com.powsybl:powsybl-commons (maven), affecting versions <= 6.7.1. It is fixed in 6.7.2. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
- Which versions of com.powsybl:powsybl-commons are affected by CVE-2025-47293? com.powsybl:powsybl-commons (maven) versions <= 6.7.1 is affected.
- Is there a fix for CVE-2025-47293? Yes. CVE-2025-47293 is fixed in 6.7.2. Upgrade to this version or later.
- Is CVE-2025-47293 exploitable, and should I be worried? Whether CVE-2025-47293 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-47293 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-47293? Upgrade
com.powsybl:powsybl-commonsto 6.7.2 or later.