CVE Intelligence
High Cryptography

CVE-2025-41669 — Insufficient Verification of Data Authenticity

The Web-based Management allows a remote low privileged Engineer user to install additional APPs on the device downloaded from the PLCnext Store without implementing any data verification mechanism, leading to the capability for an Engineer user to reach arbitrary code execution with root privileges on the PLC device. A successful exploitation may allow to install a manipulated APP package, potentially impacting integrity and availability of the PLCnext Control.

Published May 27, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: CERTVDE

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.22%
ahead of 11% of scored CVEs · Oct 14, 2026
Affects
Phoenix Contact
AXC F 1152 and 13 more
CVSS base
8.8
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Phoenix Contact AXC F 1152, Phoenix Contact AXC F 1252, Phoenix Contact AXC F 2000 EA…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Phoenix Contact AXC F 1152 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact AXC F 1252 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact AXC F 2000 EA ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact AXC F 2152 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact AXC F 3152 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact BPC 9102S ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact EPC 1522 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact RFC 4072R ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact RFC 4072S ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact VL3 UPC 2440 EDGE ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact VPLCNEXT CONTROL 1000 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact VPLCNEXT CONTROL 2000 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact VPLCNEXT CONTROL 3000 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP
Phoenix Contact VPLCNEXT CONTROL 500 ≥ 0.0.0 and < 2026.0.3 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.7 CVSS 4.0 High — — info@cert.vde.com via NIST National Vulnerability Database
8.7 CVSS 4.0 High — — CERTVDE via CVE Program (cve.org) e CISA ADP
8.8 CVSS 3.1 High 2.8 5.9 info@cert.vde.com via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High — — CERTVDE via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: info@cert.vde.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-347 · Improper Verification of Cryptographic Signature

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.22%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Check TLS negotiations and unexpected certificates in the component’s traffic.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · phoenix contact/axc f 1152, phoenix contact/axc f 1252, phoenix contact/axc f 2000 ea, phoenix contact/axc f 2152, phoen
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 27, 2026 · CERTVDE

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Phoenix Contact
every CVE for this vendor
Cryptography
same class
CWE-347
other pages naming this weakness

Related CVEs (same products)

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-41669 is "Insufficient Verification of Data Authenticity", rated High. It affects AXC F 1152 (Phoenix Contact); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.