dbcve.org
Wp 6070 Wvps FirmwareOperating system · Phoenixcontact

CVE-2023-37864

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 a remote attacker with SNMPv2 write privileges may use an a special SNMP request to gain full access to the device.

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 WP 6xxx series web panels from PHOENIX CONTACT contain an authentication bypass vulnerability where a remote attacker with SNMPv2 write privileges can send a specially crafted SNMP request to gain full administrative access to the device. This allows complete compromise of the affected panel.

MitigationUpgrade PHOENIX CONTACT WP 6xxx devices to firmware version 4.0.10 or later. If upgrading is not immediately feasible, restrict SNMP access to trusted management networks only and monitor for unauthorized SNMP write requests.

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
    Access the device web interface and navigate to System Information or Device Status to confirm the exact model number (e.g., WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, WP 6215).
    Affected if The device is any of the WP 6xxx series models listed in the affected products.
  2. Check the installed firmware version
    In the device web interface, locate the firmware version displayed in System Information, Overview, or Status page. Compare this version number against 4.0.10.
    Affected if The firmware version is below 4.0.10.
  3. Verify SNMP is enabled
    In the device web interface, navigate to the SNMP configuration section (usually under Network Settings, Services, or Security). Check whether SNMP is enabled and identify the SNMP version in use.
    Affected if SNMP is enabled and configured with SNMPv2 write access.
  4. Confirm SNMP write community string exposure
    Review SNMP access controls to determine if the SNMP write community string is accessible from untrusted networks or if the SNMP service is exposed to external interfaces.
    Affected if SNMPv2 with write privileges is accessible from management or external networks.

You are affected if you operate any Phoenix Contact WP 6xxx series panel with firmware version below 4.0.10 that has SNMPv2 enabled and accessible.

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

Upgrade PHOENIX CONTACT WP 6xxx devices to firmware version 4.0.10 or later. If upgrading is not immediately feasible, restrict SNMP access to trusted management networks only and monitor for unauthorized SNMP write requests.

Recommended fix High confidence

Firmware 4.0.10 or later 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)
  2. Check the current firmware version on the device through the web interface or console
  3. Download the firmware version 4.0.10 or later from the official PHOENIX CONTACT support website (cert.vde.com or phoenixcontact.com)
  4. Follow the standard firmware upgrade procedure documented in the device manual - typically via the web-based management interface or SD card update
  5. After upgrade, verify the firmware version has been successfully applied
  6. If SNMP is not required, consider disabling SNMPv2 to reduce attack surface

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

Fix this in Wp 6070 Wvps Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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