dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2025-10174

HIGH · 8.3 CVSS v3.1 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
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
Cleartext Transmission of Sensitive Information vulnerability in Pan Software & Information Technologies Ltd. PanCafe Pro allows Flooding. This issue affects PanCafe Pro: from < 3.3.2 through 23092025.

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

PanCafe Pro transmits sensitive information in cleartext (unencrypted) instead of using encrypted channels, potentially exposing credentials, user data, or financial transactions to network eavesdropping. The 'allows Flooding' mention suggests the vulnerability may also permit or facilitate denial-of-service conditions through cleartext protocols.

MitigationEnable TLS/SSL encryption for all network communications and upgrade PanCafe Pro to version 3.3.2 or later. Conduct a network traffic audit to identify all endpoints transmitting sensitive data in cleartext.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/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. Identify installed PanCafe Pro version
    Locate the PanCafe Pro application on the system and retrieve its version information through the application's about dialog, installation directory, or program listing
    Affected if the installed version is earlier than 3.3.2
  2. Verify network encryption configuration
    Access PanCafe Pro network settings or configuration panel and inspect whether TLS/SSL encryption is enabled for client-server communications
    Affected if TLS/SSL encryption is disabled or set to optional for sensitive communications
  3. Inspect network traffic for cleartext transmission
    Use a network capture tool to monitor PanCafe Pro traffic on applicable ports and verify whether credentials, user data, or financial information are transmitted in plaintext
    Affected if sensitive data such as usernames, passwords, or transaction details appear in cleartext within captured packets
  4. Check for cleartext protocol bindings
    Review PanCafe Pro configuration files or service settings to identify which protocols (HTTP, FTP, unencrypted database connections) are enabled for transmitting sensitive data
    Affected if unencrypted protocols are configured or enabled for handling sensitive information
  5. Examine flood/denial-of-service protections
    Look for configuration options related to flood protection, rate limiting, or connection throttling within PanCafe Pro network settings
    Affected if flood protection is disabled or cleartext protocols allow unrestricted connection volumes

A user is affected if PanCafe Pro version is earlier than 3.3.2 and sensitive data is transmitted over unencrypted channels or flood protections are absent.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable TLS/SSL encryption for all network communications and upgrade PanCafe Pro to version 3.3.2 or later. Conduct a network traffic audit to identify all endpoints transmitting sensitive data in cleartext.

Recommended fix Moderate confidence

3.3.2

  1. Upgrade PanCafe Pro to version 3.3.2 or later to resolve the cleartext transmission vulnerability
  2. After upgrading, verify that all communications are now using encrypted protocols (e.g., HTTPS, TLS)
  3. Test the updated system to ensure the flooding issue is resolved and sensitive data is no longer transmitted in cleartext

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

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