dbcve.org
Charx Sec 3000 FirmwareOperating system · Phoenixcontact

CVE-2025-25268

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 can modify configuration by sending specific requests to an API-endpoint resulting in read and write access due to missing authentication.

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 send specific requests to a vulnerable API endpoint lacking authentication, enabling them to read and write configuration data. The attack does not require credentials but requires network proximity to the target system.

MitigationImplement proper authentication and authorization controls on the affected API endpoint to ensure all configuration requests are validated before execution.

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 number
    Locate the device model label or check system information to confirm the exact model (3000, 3050, 3100, or 3150)
    Affected if The model is any of these four and the firmware version is below 1.7.3
  2. Check the installed firmware version
    Access the device web interface, admin panel, or use the command line interface to retrieve the firmware version. Look for a firmware version field in system settings or about pages.
    Affected if The firmware version is less than 1.7.3 (for example, 1.7.2, 1.6.x, or earlier)
  3. Verify API endpoint accessibility
    Determine if the device API is accessible from the network. Check network configuration to see if the API port (commonly HTTP/HTTPS on the device) is exposed to adjacent network segments.
    Affected if The API endpoint is reachable from an adjacent network without authentication barriers
  4. Test API authentication requirement
    Send a read request to the configuration API endpoint without providing any credentials or authentication tokens. Observe whether the request is accepted and returns configuration data.
    Affected if The API returns configuration data or accepts changes without requiring any authentication (no login session, API key, or token)
  5. Confirm write access without authentication
    Send a configuration modification request to the API endpoint without credentials. Check if the change is processed successfully.
    Affected if The system accepts and applies configuration changes without validating user identity

You are affected if you have a Charx Sec 3000/3050/3100/3150 device running firmware below version 1.7.3 and the API endpoint is accessible without requiring authentication.

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

Implement proper authentication and authorization controls on the affected API endpoint to ensure all configuration requests are validated before execution.

Recommended fix Moderate confidence

Firmware version 1.7.3

  1. Upgrade Charx Sec 3000 firmware to version 1.7.3 or later
  2. Upgrade Charx Sec 3050 firmware to version 1.7.3 or later
  3. Upgrade Charx Sec 3100 firmware to version 1.7.3 or later
  4. Upgrade Charx Sec 3150 firmware to version 1.7.3 or later
  5. Verify the upgrade was successful and authentication is now required for the API endpoint

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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