dbcve.org
Charx Sec 3000 FirmwareOperating system · Phoenixcontact

CVE-2025-25271

HIGH · 8.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 1.7.3 or later.
See remediation →
93/100
Remediation priority · Urgent
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 unauthenticated adjacent attacker is able to configure a new OCPP backend, due to insecure defaults for the configuration interface.

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

An unauthenticated adjacent attacker can configure a new OCPP backend on EV charging stations due to insecure default settings in the configuration interface. This allows the attacker to redirect charging station communications to a malicious backend, potentially enabling man-in-the-middle attacks, data theft, or service disruption.

MitigationChange insecure default configurations on the OCPP configuration interface to require authentication before any backend reconfiguration is allowed. Consider network segmentation to limit adjacent network attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Charx Sec 3000 FirmwareOperating system
Affected:< 1.7.3
Charx Sec 3050 FirmwareOperating system
Affected:< 1.7.3
Charx Sec 3100 FirmwareOperating system
Affected:< 1.7.3
Charx Sec 3150 FirmwareOperating system
Affected:< 1.7.3

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
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the Charx Sec model and firmware version
    Access the charging station's admin interface or check system information to determine the exact model number (3000, 3050, 3100, or 3150) and current firmware version installed
    Affected if Firmware version is below 1.7.3 for any of the Charx Sec models (3000, 3050, 3100, or 3150)
  2. Locate the OCPP configuration interface
    Navigate to the station's web-based management console or configuration panel and find the OCPP backend settings section
    Affected if The OCPP configuration interface is accessible without authentication or uses default credentials
  3. Verify backend configuration settings
    Examine the current OCPP backend URL/endpoint configuration to determine if a backend server is configured and record the current settings
    Affected if A backend URL is configured or the system allows modification of backend settings without authentication
  4. Test for authentication requirement on configuration changes
    Attempt to modify the OCPP backend configuration while unauthenticated, or review authentication settings for the configuration interface
    Affected if Backend reconfiguration is possible without providing valid authentication credentials

You are affected if you are running any Phoenixcontact Charx Sec 3000/3050/3100/3150 firmware version below 1.7.3 and the OCPP configuration interface allows unauthenticated backend reconfiguration.

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
Upgrade available Upgrade to 1.7.3 or later
Fixed in 1.7.3
Interim mitigation

Change insecure default configurations on the OCPP configuration interface to require authentication before any backend reconfiguration is allowed. Consider network segmentation to limit adjacent network attack surface.

Recommended fix High confidence

Charx Sec 3000/3050/3100/3150 Firmware >= 1.7.3

  1. Obtain firmware version 1.7.3 or later from the official Charx vendor source (certvde.com or vendor support)
  2. Access the Charx Sec device management interface via the local network (adjacent access required)
  3. Navigate to the firmware update or system maintenance section
  4. Upload and apply the firmware version 1.7.3
  5. Verify the upgrade was successful by checking the firmware version in the device status
  6. After upgrade, verify that the configuration interface now requires proper authentication before allowing OCPP backend changes

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

Fix this in Charx Sec 3000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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