dbcve.org
Freeflow CoreApplication · Xerox

CVE-2026-2252

HIGH · 7.5 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 8.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An XML External Entity (XXE) vulnerability allows malicious user to perform Server-Side Request Forgery (SSRF) via crafted XML input containing malicious external entity references. This issue affects Xerox FreeFlow Core versions up to and including 8.0.7.  Please consider upgrading to FreeFlow Core version 8.1.0 via the software available on -  https://www.support.xerox.com/en-us/product/core/downloads

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 · high confidence

An XML External Entity (XXE) vulnerability in Xerox FreeFlow Core versions up to 8.0.7 allows remote attackers to perform Server-Side Request Forgery (SSRF) by submitting crafted XML input containing malicious external entity references. This can enable attackers to make the affected server make arbitrary requests to internal or external resources.

MitigationUpgrade Xerox FreeFlow Core to version 8.1.0 which contains the patch for this XXE vulnerability.

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
Freeflow CoreApplication
Affected:< 8.1.0

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Xerox FreeFlow Core installation
    Search for Xerox FreeFlow Core installation directories or check common installation paths (e.g., C:\Program Files\Xerox\FreeFlow Core or /opt/xerox/freeflow-core)
    Affected if Xerox FreeFlow Core is installed on the system
  2. Identify installed version
    Check the version information in the installation directory, typically found in an About dialog, version.txt, or product metadata files
    Affected if The installed version is lower than 8.1.0 (versions up to 8.0.7 are affected)
  3. Verify XML processing functionality
    Examine the web interfaces or API endpoints that accept XML input. Look for document conversion, import, or print job submission features that process XML documents
    Affected if The system exposes functionality that processes user-submitted XML documents without restricting external entities
  4. Check network accessibility
    Review firewall rules and network configuration to determine if the XML processing endpoints are accessible from untrusted networks
    Affected if The XML processing interfaces are exposed to untrusted network segments or the internet

You are affected if Xerox FreeFlow Core is installed with a version below 8.1.0 and the system exposes XML processing functionality to users or network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.1.0 or later
Fixed in 8.1.0
Interim mitigation

Upgrade Xerox FreeFlow Core to version 8.1.0 which contains the patch for this XXE vulnerability.

Recommended fix High confidence

FreeFlow Core 8.1.0

  1. Navigate to the Xerox support website at https://www.support.xerox.com/en-us/product/core/downloads
  2. Download the FreeFlow Core version 8.1.0 software
  3. Follow the standard Xerox FreeFlow Core upgrade procedure to install version 8.1.0
  4. Verify the installation by checking that the FreeFlow Core version is reported as 8.1.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freeflow Core Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2252 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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