dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-10639

HIGH · 8.8 CVSS v3.1 Published 2025-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The WorkExaminer Professional server installation comes with an FTP server that is used to receive the client logs on TCP port 12304. An attacker with network access to this port can use weak hardcoded credentials to login to the FTP server and modify or read data, log files and gain remote code execution as NT Authority\SYSTEM on the server by exchanging accessible service binaries in the WorkExaminer installation directory (e.g. "C:\Program File (x86)\Work Examiner Professional Server").

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

The WorkExaminer Professional server ships with an FTP service on TCP port 12304 that uses weak hardcoded credentials, allowing any network-attacker to authenticate. Once authenticated, the attacker can replace service binaries in the installation directory to achieve remote code execution as NT Authority\SYSTEM.

MitigationImmediately change the hardcoded FTP credentials to strong, unique values, disable the FTP service if unused, and restrict network access to port 12304 to authorized IPs only. Consider replacing service binaries with immutable locations and applying least-privilege principles to the service account.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm WorkExaminer Professional is installed
    Look for the product in installed programs (Control Panel > Programs and Features) or check common installation paths such as C:\Program Files\WorkExaminer or C:\Program Files (x86)\WorkExaminer for the executable files.
    Affected if WorkExaminer Professional is present on the system.
  2. Identify the installed version
    Right-click the WorkExaminer executable (usually workexaminer.exe or wexaminer.exe in the installation directory), select Properties, and note the File Version on the Details tab. Alternatively, run: dir "C:\Program Files\WorkExaminer" /s /b 2>nul or dir "C:\Program Files (x86)\WorkExaminer" /s /b 2>nul
    Affected if The installed version falls within any affected version range (compare your version to the vendor's advisory).
  3. Verify FTP service is running on port 12304
    Open Command Prompt and run: netstat -ano | findstr :12304. Also check via Services console (services.msc) for a service named WorkExaminer FTP or similar, or run: sc query type= service state= all | findstr -i workexaminer
    Affected if TCP port 12304 is listening or a WorkExaminer-related FTP service is running.
  4. Check if FTP accepts hardcoded credentials
    Attempt an anonymous or default credential login to the FTP server on port 12304 using an FTP client: ftp <targetIP> 12304. Try common default credentials such as admin/admin, workexaminer/workexaminer, or anonymous/anonymous. If login succeeds without the administrator changing the password, the system is vulnerable.
    Affected if The FTP service authenticates using hardcoded/default credentials accessible to any network attacker.
  5. Determine network exposure of port 12304
    Run: netsh firewall show all or check Windows Defender Firewall advanced security rules for inbound rules on port 12304. Also verify external exposure by scanning the IP from an external network or reviewing perimeter firewall rules.
    Affected if Port 12304 is accessible from untrusted networks (Internet, guest WiFi, or other non-admin network segments).

The environment is affected if WorkExaminer Professional with a vulnerable version is installed, the FTP service on port 12304 is running, and it uses hardcoded credentials that are accessible from a network where attackers can reach port 12304.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change the hardcoded FTP credentials to strong, unique values, disable the FTP service if unused, and restrict network access to port 12304 to authorized IPs only. Consider replacing service binaries with immutable locations and applying least-privilege principles to the service account.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10639 — 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-2025-10639 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