dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-6950

CRITICAL · 9.9 CVSS v4.0 Published 2025-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
An Use of Hard-coded Credentials vulnerability has been identified in Moxa’s network security appliances and routers. The system employs a hard-coded secret key to sign JSON Web Tokens (JWT) used for authentication. This insecure implementation allows an unauthenticated attacker to forge valid tokens, thereby bypassing authentication controls and impersonating any user. Exploitation of this vulnerability can result in complete system compromise, enabling unauthorized access, data theft, and full administrative control over the affected device. While successful exploitation can severely impact the confidentiality, integrity, and availability of the affected device itself, there is no loss of confidentiality or integrity within any subsequent systems.

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

Moxa network security appliances use a hard-coded secret key to sign JSON Web Tokens (JWT) for authentication. An unauthenticated attacker can exploit this by forging valid JWTs using the known hard-coded key, completely bypassing authentication and gaining administrative access to the affected device.

MitigationApply vendor-supplied firmware updates or patches that replace the hard-coded JWT signing key with a properly managed secret. If no patch is available, implement network segmentation, restrict management interface exposure, and monitor for unauthorized access attempts.

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:H/VA:H/SC:N/SI:N/SA:H/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 checks

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

  1. Identify Moxa network security appliance
    Check the device model and manufacturer through the web interface, SNMP, or by inspecting the device label. Moxa appliances typically have model numbers such as NPX series, OnCell series, or secure routers.
    Affected if The device is a Moxa network security appliance (firewall, VPN gateway, or secure router).
  2. Determine firmware version
    Access the device web interface and navigate to System > Status or System > Firmware to view the current firmware version. Alternatively, use the CLI command 'show version' or SNMP OID 1.3.6.1.2.1.47.1.1.1.1.9 to retrieve it.
    Affected if The installed firmware version contains the hardcoded JWT signing key (compare your version to vendor advisories for CVE-2025-6950).
  3. Verify JWT authentication is enabled
    Inspect the device's authentication settings in the web interface under User Management, Access Control, or Authentication settings. Look for configurations that enable token-based or JWT-based login for the admin or user portals.
    Affected if JWT-based authentication is enabled and used for web UI or API access.
  4. Inspect firmware or config for hardcoded key strings
    If you have access to the firmware image or backup configuration files, search for common JWT-related strings such as 'JWT', 'secret', 'signingKey', or examine the authentication module binaries for embedded cryptographic material.
    Affected if A static or hardcoded string used for JWT signing is found embedded in the firmware or configuration.

If the device is a Moxa network security appliance with JWT authentication enabled running a firmware version that contains the hardcoded signing key, the environment is affected by CVE-2025-6950.

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

Apply vendor-supplied firmware updates or patches that replace the hard-coded JWT signing key with a properly managed secret. If no patch is available, implement network segmentation, restrict management interface exposure, and monitor for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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