dbcve.org
Wp 6070 Wvps FirmwareOperating system · Phoenixcontact

CVE-2023-37859

HIGH · 7.2 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 4.0.10 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
In PHOENIX CONTACTs WP 6xxx series web panels in versions prior to 4.0.10 the SNMP daemon is running with root privileges allowing a remote attacker with knowledge of the SNMPv2 r/w community string to execute system commands as root.

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 · high confidence

The SNMP daemon on PHOENIX CONTACT WP 6xxx series web panels runs with root privileges. A remote attacker who possesses the SNMPv2 read/write community string can send specially crafted SNMP requests to execute arbitrary system commands with root-level privileges, achieving unauthenticated remote code execution with maximum system privileges.

MitigationUpdate affected devices to firmware version 4.0.10 or later. Additionally, change the default SNMP community strings to strong, unique values and restrict SNMP access through network segmentation or firewall rules to prevent unauthorized external access.

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
Wp 6070 Wvps FirmwareOperating system
Affected:< 4.0.10
Wp 6101 Wxps FirmwareOperating system
Affected:< 4.0.10
Wp 6121 Wxps FirmwareOperating system
Affected:< 4.0.10
Wp 6156 Whps FirmwareOperating system
Affected:< 4.0.10
Wp 6185 Whps FirmwareOperating system
Affected:< 4.0.10
Wp 6215 Whps FirmwareOperating system
Affected:< 4.0.10

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

CVSS:3.1/AV:N/AC:L/PR:H/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 device model
    Determine the exact Phoenix Contact WP series model number (WP 6070, 6101, 6121, 6156, 6185, or 6215) by checking the device label, web interface, or system information.
    Affected if The device is one of the WP 6xxx series models listed in the affected products.
  2. Check the installed firmware version
    Access the device web interface or use SNMP sysDescr OID (1.3.6.1.2.1.1.1) to retrieve the firmware version. Compare it against the affected version range.
    Affected if The firmware version is below 4.0.10.
  3. Verify SNMP service status
    Check if the SNMP service is enabled and accessible by sending an SNMP request to UDP port 161 or by checking the device configuration for SNMP settings.
    Affected if SNMP is enabled and reachable on the network.
  4. Check SNMP community string configuration
    Review the SNMP community string configuration. Determine if the default read/write community string is still in use or if a weak community string is configured.
    Affected if A default, weak, or easily guessable SNMP read/write community string is configured.
  5. Assess network exposure of SNMP port
    Verify whether UDP port 161 is exposed to untrusted networks or the internet by reviewing firewall rules, network segmentation, and access control lists.
    Affected if SNMP port 161 is accessible from untrusted or external network segments.

A user is affected if they have a WP 6xxx series device (6070, 6101, 6121, 6156, 6185, or 6215) running firmware below version 4.0.10 with SNMP enabled and accessible using a default or weak community string.

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 4.0.10 or later
Fixed in 4.0.10
Interim mitigation

Update affected devices to firmware version 4.0.10 or later. Additionally, change the default SNMP community strings to strong, unique values and restrict SNMP access through network segmentation or firewall rules to prevent unauthorized external access.

Recommended fix High confidence

Firmware version 4.0.10 for WP 6xxx series

  1. Identify the specific WP 6xxx model (WP 6070 WVPS, WP 6101 WXPS, WP 6121 WXPS, WP 6156 WHPS, WP 6185 WHPS, or WP 6215 WHPS) in your environment
  2. Download the firmware version 4.0.10 or later from the official PHOENIX CONTACT support website (cert.vde.com or phoenixcontact.com)
  3. Review the firmware upgrade instructions provided by PHOENIX CONTACT for your specific device model
  4. Backup the current device configuration before performing the firmware upgrade
  5. Upload and apply firmware version 4.0.10 to the affected device via the web interface or management tool
  6. Verify the firmware version has been successfully applied
  7. After upgrade, verify the SNMP daemon is no longer running with root privileges
  8. Change the SNMPv2 community strings from default values to strong, unique values
Caveat Review release notes for any compatibility changes or configuration adjustments required after upgrading to 4.0.10

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

Fix this in Wp 6070 Wvps Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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