CVE-2026-39907
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 · uneditedUnisys WebPerfect Image Suite versions 3.0.3960.22810 and 3.0.3960.22604 expose an unauthenticated WCF SOAP endpoint on TCP port 1208 that accepts unsanitized file paths in the ReadLicense action's LFName parameter, allowing remote attackers to trigger SMB connections and leak NTLMv2 machine-account hashes. Attackers can submit crafted SOAP requests with UNC paths to force the server to initiate outbound SMB connections, exposing authentication credentials that may be relayed for privilege escalation or lateral movement within the network.
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 confidenceUnisys WebPerfect Image Suite versions 3.0.3960.22810 and 3.0.3960.22604 expose an unauthenticated WCF SOAP endpoint on TCP port 1208. The ReadLicense action's LFName parameter accepts unsanitized file paths, including UNC paths, allowing attackers to force the server to initiate outbound SMB connections to attacker-controlled locations. This causes the server's NTLMv2 machine-account hash to be transmitted and captured by the attacker, enabling relay attacks for privilege escalation or lateral movement.
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= 3.0.3960.22604= 3.0.3960.22810CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
-
Identify Unisys WebPerfect Image Suite installationSearch the system for Unisys WebPerfect Image Suite software. Check installed programs via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or use system inventory tools. Look for any Unisys-related services running.Affected if Unisys WebPerfect Image Suite is installed on the system
-
Verify installed version against affected releasesLocate the installed version number. Check the software's About or Version information, or examine the executable file properties of the main Unisys WebPerfect binaries. Compare your version to 3.0.3960.22604 and 3.0.3960.22810.Affected if The installed version is exactly 3.0.3960.22604 or 3.0.3960.22810
-
Confirm TCP port 1208 is listeningRun netstat -an | findstr :1208 or use PowerShell Get-NetTCPConnection -LocalPort 1208 to check if the WCF SOAP endpoint is bound to TCP port 1208.Affected if Port 1208 is listening and accepting connections
-
Test ReadLicense action for parameter injectionSend a crafted SOAP request to the endpoint at port 1208 with an XML payload targeting the ReadLicense action. Include a UNC path (e.g., \\attacker-server\share) in the LFName parameter. Monitor for outbound SMB connection attempts using network capture or Windows Event Log events 4624/4625 for authentication attempts to unexpected targets.Affected if The endpoint accepts the request and triggers outbound SMB/TCP connections to arbitrary UNC paths via the LFName parameter
-
Check for anomalous outbound SMB authenticationReview Windows Security Event Logs for NTLM authentication events (Event ID 4624) with unusual source IP addresses. Use network monitoring to detect SMB sessions initiated from the server to untrusted or external IP addresses on ports 445 or 139.Affected if Outbound SMB connections are observed originating from the server to hosts not in the local network
The environment is affected if Unisys WebPerfect Image Suite version 3.0.3960.22604 or 3.0.3960.22810 is installed with TCP port 1208 exposed and the ReadLicense SOAP endpoint responds to UNC path injection attempts.
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 dataBlock inbound access to TCP port 1208 from untrusted networks, disable the vulnerable WCF SOAP endpoint if not required for business functions, and implement SMB signing to prevent NTLM relay attacks. If a vendor patch becomes available, apply it promptly.
- 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-2026-39907 — 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-2026-39907 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