CVE-2025-10641
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 · uneditedAll WorkExaminer Professional traffic between monitoring client, console and server is transmitted as plain text. This allows an attacker with access to the network to read the transmitted sensitive data. An attacker can also freely modify the data on the wire. The monitoring clients transmit their data to the server using the unencrypted FTP. Clients connect to the FTP server on port 12304 and transmit the data unencrypted. In addition, all traffic between the console client and the server at port 12306 is unencrypted.
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 confidenceWorkExaminer Professional transmits all monitoring data in plain text between clients, console, and server. Monitoring clients use unencrypted FTP on port 12304 to send data to the server, and console-to-server communication on port 12306 is also unencrypted. This allows network attackers to intercept sensitive monitoring data and modify it in transit.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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.
-
Identify if WorkExaminer Professional is installedCheck installed programs list or look for WorkExaminer installation directory on the systemAffected if WorkExaminer Professional is present on the system
-
Verify if port 12304 is listening and using FTPRun netstat or similar tool to check if port 12304 is open and listening for FTP connectionsAffected if Port 12304 is open and accepting unencrypted FTP connections
-
Verify if port 12306 is in use for console-server communicationRun netstat or similar tool to check if port 12306 is open and being used for console-server communicationAffected if Port 12306 is open and accepting unencrypted connections
-
Capture network traffic on ports 12304 and 12306Use a network packet capture tool (such as Wireshark) to monitor traffic on ports 12304 and 12306 and verify data is transmitted in plain textAffected if Network traffic on these ports is visible in plain text without TLS/SSL or encryption wrapping
-
Check FTP server configuration on the WorkExaminer serverExamine the WorkExaminer server configuration files or settings to confirm FTP is enabled without TLS/SSL encryption (FTPS)Affected if FTP is configured in plain text mode without encryption
A user is affected if WorkExaminer Professional is installed and network traffic analysis confirms unencrypted data transmission on ports 12304 (FTP) or 12306 (console-server).
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 dataReplace unencrypted protocols with secure alternatives: migrate from FTP to SFTP or FTPS for client data transfer, and implement TLS/SSL encryption for console-server communications on port 12306.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10641 — 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-10641 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