CVE-2025-25270: An unauthenticated remote attacker can alter the device configuration in a way to get remote code execution as

Q: How do I fix CVE-2025-25270?

charx sec-3000 firmware: upgrade to 1.7.3; charx sec-3050 firmware: upgrade to 1.7.3; charx sec-3100 firmware: upgrade to 1.7.3. Exact commands for each OS are on this page.

Q: Is CVE-2025-25270 being exploited?

CVE-2025-25270 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-25270 affect?

CVE-2025-25270 affects charx sec-3000 firmware, charx sec-3050 firmware, charx sec-3100 firmware. Severity is critical (CVSS 9.8). An unauthenticated remote attacker can alter the device configuration in a way to get remote code execution as root with specific configurations.

Q: How urgent is CVE-2025-25270?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADEUPGRADEUPGRADE

CVE-2025-25270 is a critical-severity flaw (CVSS 9.8) affecting charx sec-3000 firmware, charx sec-3050 firmware, charx sec-3100 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An unauthenticated remote attacker can alter the device configuration in a way to get remote code execution as root with specific configurations.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Weakness	CWE-913
Published	2025-07-08
Last modified	2026-06-17

Publisher (CNA): CERT VDE · Vendor: phoenixcontact

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-07-08 07:15 UTCPublished CVE record published
2026-06-17 09:00 UTCUpdated Record last modified

phoenixcontact charx sec-3000 firmware UPGRADE

Affected: < 1.7.3

Fixed in: 1.7.3

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

phoenixcontact charx sec-3050 firmware UPGRADE

Affected: < 1.7.3

Fixed in: 1.7.3

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

phoenixcontact charx sec-3100 firmware UPGRADE

Affected: < 1.7.3

Fixed in: 1.7.3

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

phoenixcontact charx sec-3150 firmware UPGRADE

Affected: < 1.7.3

Fixed in: 1.7.3

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-25270?

charx sec-3000 firmware: upgrade to 1.7.3; charx sec-3050 firmware: upgrade to 1.7.3; charx sec-3100 firmware: upgrade to 1.7.3. Exact commands for each OS are on this page.

Is CVE-2025-25270 being exploited?

CVE-2025-25270 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-25270 affect?

CVE-2025-25270 affects charx sec-3000 firmware, charx sec-3050 firmware, charx sec-3100 firmware. Severity is critical (CVSS 9.8). An unauthenticated remote attacker can alter the device configuration in a way to get remote code execution as root with specific configurations.

How urgent is CVE-2025-25270?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-25271 HIGH 8.8 UPGRADE UPGRADE An unauthenticated adjacent attacker is able to configure a new OCPP backend, due to insecure defaults for the
CVE-2025-25269 HIGH 8.4 UPGRADE UPGRADE An unauthenticated local attacker can inject a command that is subsequently executed as root, leading to a pri
CVE-2025-25268 HIGH 8.8 UPGRADE UPGRADE An unauthenticated adjacent attacker can modify configuration by sending specific requests to an API-endpoint
CVE-2025-24006 HIGH 7.8 UPGRADE UPGRADE A low privileged local attacker can leverage insecure permissions via SSH on the affected devices to escalate
CVE-2025-24005 HIGH 7.8 UPGRADE UPGRADE A local attacker with a local user account can leverage a vulnerable script via SSH to escalate privileges to

References

← Back to latest CVEs