CVE-2025-34350
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 · uneditedUnForm Server versions < 10.1.15 contain an unauthenticated arbitrary file read and SMB coercion vulnerability in the Doc Flow feature’s 'arc' endpoint. The Doc Flow module uses the 'arc' handler to retrieve and render pages or resources specified by the user-supplied 'pp' parameter, but it does so without enforcing authentication or restricting path inputs. As a result, an unauthenticated remote attacker can supply local filesystem paths to read arbitrary files accessible to the service account. On Windows deployments, providing a UNC path can also coerce the server into initiating outbound SMB authentication, potentially exposing NTLM credentials for offline cracking or relay. This issue may lead to sensitive information disclosure and, in some environments, enable further lateral movement.
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 confidenceUnForm Server versions before 10.1.15 have an unauthenticated arbitrary file read vulnerability in the Doc Flow module's 'arc' endpoint. The 'pp' parameter accepts user-supplied paths without validation or authentication, allowing remote attackers to read any file accessible to the service account. On Windows, providing a UNC path triggers outbound SMB connections that can expose NTLM credentials for relay or cracking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Determine UnForm Server versionCheck the installed UnForm Server version through the administration console, software inventory, or running 'ufserver -v' if available. Compare the version number to the 10.1.15 threshold.Affected if Installed version is below 10.1.15 (e.g., 10.1.14, 10.0.x, 9.x)
-
Confirm Doc Flow module is enabledInspect UnForm Server configuration files or admin interface to verify the Doc Flow module is installed and active. Look for 'DocFlow' or 'arc' related configuration entries.Affected if Doc Flow module is installed and enabled on the server
-
Verify network accessibility of the arc endpointTest HTTP/HTTPS access to the '/arc' endpoint of the Doc Flow service. Attempt a request to the endpoint (e.g., GET /docflow/arc or similar path based on your installation).Affected if The arc endpoint is reachable over the network without authentication
-
Check for unauthenticated pp parameter accessSend a request to the arc endpoint with a test 'pp' parameter pointing to a non-sensitive file (e.g., ?pp=/etc/hosts on Linux). Observe if the file content is returned.Affected if The pp parameter accepts arbitrary file paths without authentication and returns file contents
-
Assess Windows SMB exposureIf the server runs Windows, determine if outbound SMB traffic (ports 445, 139) is permitted through the firewall. Check if UNC path input triggers outbound connections.Affected if Server is Windows-based and allows outbound SMB traffic, enabling NTLM credential exposure via UNC paths
The environment is affected if UnForm Server version is below 10.1.15 AND the Doc Flow module with its unauthenticated arc endpoint is accessible over the network.
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.
dbcve · scopedUpgrade to UnForm Server version 10.1.15 or later. As interim measures, restrict network access to the Doc Flow endpoint and block outbound SMB traffic at the perimeter to prevent NTLM relay attacks.
10.1.15
- Identify the current UnForm Server version running in the environment
- Obtain UnForm Server version 10.1.15 or later from the official vendor (unform.com)
- Backup the current UnForm Server configuration and data directories before upgrading
- Apply the upgrade to UnForm Server version 10.1.15 or later following vendor documentation
- Verify the Doc Flow 'arc' endpoint now requires authentication and properly sanitizes the 'pp' parameter
- Confirm the vulnerability is remediated by attempting (and failing) to access arbitrary files via the 'pp' parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34350 — 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-34350 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