nday
CVE-2025-41696

Hardcoded User Password

Phoenix Contact / FL SWITCH 2005, FL SWITCH 2008, FL SWITCH 2016, FL SWITCH 2105, FL SWITCH 2108, FL SWITCH 2116 +63

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

hard-coded credentials
CWE-798, stated by the CNA CERTVDE and NVD, republishing [email protected]
physical
AV:P in CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (CVSS 3.1) from the CNA CERTVDE
no authentication required
PR:N in CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (CVSS 3.1) from the CNA CERTVDE
no user interaction
UI:N in CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (CVSS 3.1) from the CNA CERTVDE
ICS / OT
affected products in the CVE record: Phoenix Contact · FL NAT 2008, Phoenix Contact · FL NAT 2208, Phoenix Contact · FL NAT 2304-2GC-2SFP, Phoenix Contact · FL SWITCH 2005, Phoenix Contact · FL SWITCH 2008, Phoenix Contact · FL SWITCH 2008F, Phoenix Contact · FL SWITCH 2016, Phoenix Contact · FL SWITCH 2105, Phoenix Contact · FL SWITCH 2108, Phoenix Contact · FL SWITCH 2116 and 59 moreCPE names NVD's analysts give as vulnerable: o:phoenixcontact:fl_nat_2008_firmware, o:phoenixcontact:fl_nat_2208_firmware, o:phoenixcontact:fl_nat_2304-2gc-2sfp_firmware, o:phoenixcontact:fl_switch_2005_firmware, o:phoenixcontact:fl_switch_2008_firmware, o:phoenixcontact:fl_switch_2008f_firmware, o:phoenixcontact:fl_switch_2016_firmware, o:phoenixcontact:fl_switch_2105_firmware, o:phoenixcontact:fl_switch_2108_firmware, o:phoenixcontact:fl_switch_2116_firmware and 59 morenday's type rule vendor:phoenix-contact
stage
DIS
disclosed
cvss
4.6 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2025-12-09T08:13Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

An attacker can use an undocumented UART port on the PCB as a side-channel with the user hardcoded credentials obtained from CVE-2025-41692 to gain read access to parts of the filesystem of the device.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:P
Physical: needs physical access to the device
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA CERTVDE.

Event log

+DISdisclosed

CVE record published by CERTVDE. CVSS 4.6, medium.

src cvelist · nday , bulk import · raw
{
  "id": 376432,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-41696",
  "occurred_at": "2025-12-09T08:13:22.783Z",
  "observed_at": "2026-11-13T05:39:08.090137Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "version": "3.1",
      "base_score": 4.6,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2025-12-09T14:32:56.219284Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2025-12-09T08:13:22.783Z",
    "assigner_short_name": "CERTVDE"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.