dbcve.org
Charx Sec 3000 FirmwareOperating system · Phoenixcontact

CVE-2025-24005

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 1.7.3 or later.
See remediation →
80/100
Remediation priority · High
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
A local attacker with a local user account can leverage a vulnerable script via SSH to escalate privileges to root due to improper input validation.

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

A local attacker with an existing user account can SSH into the system and execute a vulnerable script that lacks proper input validation, allowing the attacker to inject malicious parameters and escalate privileges to root.

MitigationImplement strict input validation and sanitization on all scripts executable via SSH, following the principle of least privilege to limit what low-privilege users can execute.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 Phoenix Contact Charx Sec device model
    Check system information or product labeling to confirm the device is a Charx Sec 3000, 3050, 3100, or 3150 model
    Affected if The device is not one of these four models, then it is not affected by this CVE
  2. Determine the installed firmware version
    Access the device web interface or check system files for firmware version information; compare against 1.7.3
    Affected if Firmware version is lower than 1.7.3 (for example, 1.7.2, 1.6.x, etc.)
  3. Verify SSH access is enabled on the device
    Check the device configuration or running services to confirm the SSH service is active and accessible
    Affected if SSH is disabled or blocked, the attack surface does not exist for this vector
  4. Confirm low-privilege user accounts exist and can authenticate via SSH
    Review the list of local users and check SSH authentication configuration (such as authorized_keys or password-based SSH access settings)
    Affected if No regular (non-root) user accounts have SSH access, the specific attack path is not available
  5. Check if any scripts are executable via the SSH user account
    Review the SSH command configuration or shell access restrictions for standard user accounts to see what scripts or commands they can invoke
    Affected if Users have unrestricted or poorly restricted script execution capabilities via SSH, the input validation flaw can be triggered

The device is affected if it is a Phoenix Contact Charx Sec 3000/3050/3100/3150 with firmware version below 1.7.3 and SSH access is available for non-root users who can execute scripts through the SSH connection.

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 strict input validation and sanitization on all scripts executable via SSH, following the principle of least privilege to limit what low-privilege users can execute.

Recommended fix Moderate confidence

Charx Sec Firmware 1.7.3

  1. Obtain Charx Sec firmware version 1.7.3 or later from the vendor (certvde.com or official Charx supplier)
  2. Follow the vendor's standard firmware upgrade procedure for your Charx Sec model (3000, 3050, 3100, or 3150)
  3. Verify the upgrade was successful by confirming the firmware version is 1.7.3 or later
  4. Ensure SSH access is properly secured after upgrade (use key-based authentication, disable root login if possible)

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

Fix this in Charx Sec 3000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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