dbcve.org
Charx Sec 3000 FirmwareOperating system · Phoenixcontact

CVE-2024-25996

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 1.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 remote attacker can perform a remote code execution due to an origin validation error. The access is limited to the service user.

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

This is an unauthenticated remote code execution vulnerability caused by an origin validation error, likely a CORS (Cross-Origin Resource Sharing) misconfiguration that allows arbitrary cross-origin requests without proper validation. An attacker can exploit this to execute code within the context of the service user account.

MitigationImplement strict origin validation by explicitly whitelisting trusted origins, implementing proper CORS headers with appropriate Access-Control-Allow-Origin policies, and adding CSRF tokens for state-changing operations.

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.5.1
Charx Sec 3050 FirmwareOperating system
Affected:< 1.5.1
Charx Sec 3100 FirmwareOperating system
Affected:< 1.5.1
Charx Sec 3150 FirmwareOperating system
Affected:< 1.5.1

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

CVSS:3.1/AV:N/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 device model
    Access the device web interface or use SNMP/network discovery to confirm the exact model is one of: Charx Sec 3000, Charx Sec 3050, Charx Sec 3100, or Charx Sec 3150
    Affected if Device model is any of the four listed models
  2. Check firmware version
    Log into the device web interface and navigate to System > Firmware or System > Information page to view the installed firmware version, or use the manufacturer's management software to query the firmware version
    Affected if Firmware version is below 1.5.1 (for example, 1.4.x, 1.3.x, etc.)
  3. Verify web service is enabled
    Check if the device web management interface is accessible over HTTP/HTTPS from the network, or inspect device network configuration for web service status
    Affected if Web interface is enabled and reachable on the network (required for the CORS vulnerability to be exploitable)
  4. Inspect CORS configuration
    If accessible, examine the device API or web service configuration files for Access-Control-Allow-Origin headers or CORS policy settings. Use browser developer tools or curl with Origin header to test CORS behavior
    Affected if CORS policy allows arbitrary origins or lacks origin validation (response includes Access-Control-Allow-Origin: * or reflects the Origin header without validation)

If the device is a Charx Sec 3000/3050/3100/3150 with firmware version below 1.5.1 and has the web management interface enabled, the environment is likely affected by this CORS misconfiguration vulnerability.

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.5.1 or later
Fixed in 1.5.1
Interim mitigation

Implement strict origin validation by explicitly whitelisting trusted origins, implementing proper CORS headers with appropriate Access-Control-Allow-Origin policies, and adding CSRF tokens for state-changing operations.

Recommended fix Moderate confidence

Charx Sec 3000/3050/3100/3150 Firmware version 1.5.1

  1. Obtain Charx Sec 3000/3050/3100/3150 firmware version 1.5.1 from the vendor (Charx) via official channels
  2. Verify the firmware integrity using checksums provided by the vendor
  3. Access the device management interface or use the vendor's firmware update mechanism
  4. Upload and apply firmware version 1.5.1 to the affected Charx Sec device
  5. Confirm the upgrade was successful and the device is operational
  6. Verify the device is no longer vulnerable by confirming firmware version 1.5.1 is running

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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