CVE-2025-8355
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceXerox FreeFlow Core 8.0.4 contains an XXE (XML External Entity) vulnerability where improper handling of XML input allows injection of external entity references. Attackers can embed malicious external entity declarations in XML that cause the server to make unauthorized requests to internal URLs, resulting in SSRF.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Xerox FreeFlow Core installation and versionLocate the Xerox FreeFlow Core installation directory and check the version information file or application metadata. Typical locations include C:\Program Files\Xerox\FreeFlow Core or /opt/xerox/freeflow-core. Look for version.txt, about.ini, or check the application properties panel.Affected if The installed version is exactly 8.0.4
-
Identify XML input processing featuresExamine the application configuration files for XML-related processing settings. Look for XML parser configuration, job submission templates, or XML import functionality. Check configuration files in the conf or config subdirectory of the installation path.Affected if XML processing features are enabled and the application accepts XML input from users or external sources
-
Verify XML parser external entity configurationLocate the XML parser configuration file (commonly parser.xml, xerces-config.xml, or within the main application config). Inspect the parser settings for doctype, external entity, or DTD processing flags.Affected if The XML parser is configured to allow external entity processing (dtd or external-dtd-entries enabled) rather than being set to deny external entities
-
Check for SSRF-accessible XML endpointsReview web service configurations, API endpoints, or job submission interfaces that accept XML payloads. Determine if these endpoints are exposed to untrusted networks or users.Affected if XML input endpoints are accessible without proper network segmentation or authentication
A user is affected if Xerox FreeFlow Core version 8.0.4 is installed AND the application accepts XML input through any feature with the XML parser configured to permit external entity processing.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable external entity processing in the XML parser configuration and implement strict XML input validation to prevent entity expansion from untrusted sources.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8355 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data