CVE-2025-8355VulnerabilityPublished 8 Aug 2025

CVE-2025-8355: Xerox FreeFlow Core · XML External Entity (XXE)

Affects Xerox FreeFlow CoreSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 8.8% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Xerox FreeFlow Core	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-8355 effectively, European organizations should: 1) Immediately verify the version of Xerox FreeFlow Core in use and prioritize upgrading to a patched version once available from Xerox. 2) Implement network-level controls to restrict outbound HTTP/HTTPS requests from the FreeFlow Core server to only trusted destinations, minimizing the SSRF attack surface. 3) Employ Web Application Firewalls (WAFs) with rules designed to detect and block suspicious XML payloads or unusual request patterns indicative of XXE or SSRF attempts. 4) Disable or restrict XML external entity processing in the application configuration or underlying XML parsers if configurable, to prevent resolution of external entities. 5) Conduct internal network segmentation to isolate print workflow servers from critical internal services, limiting the potential impact of SSRF exploitation. 6) Monitor logs and network traffic for anomalous requests originating from the FreeFlow Core server that could indicate exploitation attempts. 7) Educate IT and security teams about the vulnerability to ensure rapid detection and response. These steps go beyond generic advice by focusing on network controls, configuration hardening, and monitoring tailored to the nature of the vulnerability and the affected product.

Description

In Xerox FreeFlow Core version 8.0.4, improper handling of XML input allows injection of external entities. An attacker can craft malicious XML containing references to internal URLs, this results in a Server-Side Request Forgery (SSRF).

Impact

For European organizations, the impact of CVE-2025-8355 can be significant, especially for those utilizing Xerox FreeFlow Core in their print and document workflow infrastructures. The SSRF vulnerability could allow attackers to pivot from the compromised print server into internal networks, potentially accessing sensitive internal web services, databases, or administrative interfaces that are not exposed externally. This can lead to unauthorized disclosure of confidential information, including internal documents, user credentials, or configuration data. Given the high confidentiality impact, organizations handling sensitive or regulated data (e.g., financial institutions, healthcare providers, government agencies) are at increased risk of data breaches or compliance violations under GDPR. The lack of required authentication and user interaction means the vulnerability can be exploited remotely and autonomously, increasing the risk of automated scanning and exploitation attempts. Although no known exploits are currently reported, the public disclosure and high CVSS score may prompt attackers to develop exploits rapidly. Additionally, SSRF can be a stepping stone for more complex attacks, such as lateral movement or privilege escalation within the network. The impact on operational continuity is limited since the vulnerability does not affect integrity or availability directly, but the confidentiality breach alone can have severe reputational and financial consequences.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

securitydocs.business.xerox.com/wp-content/uploads/2025/08/Xerox-Security-Bulletin-025-013-for-Freeflow-Core-8.0.5.pdf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Aug 2025, 16:03 UTC

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats