dbcve.org
Wp 6070 Wvps FirmwareOperating system · Phoenixcontact

CVE-2023-37860

HIGH · 7.5 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 4.0.10 or later.
See remediation →
84/100
Remediation priority · High
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
In PHOENIX CONTACTs WP 6xxx series web panels in versions prior to 4.0.10 a remote unauthenticated attacker can obtain the r/w community string of the SNMPv2 daemon.

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 SNMPv2 daemon that exposes the read/write community string to unauthenticated remote attackers in versions prior to 4.0.10. An attacker can retrieve this credential without any authentication, potentially gaining write access to the device's SNMP configuration.

MitigationUpgrade the WP 6xxx firmware to version 4.0.10 or later. If immediate patching is not feasible, restrict network access to the affected devices and consider implementing SNMPv3 which supports authentication and encryption.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 panel or check the device label to confirm it is one of the following models: WP 6070 WVPS, WP 6101 WXPS, WP 6121 WXPS, WP 6156 WHPS, WP 6185 WHPS, or WP 6215 WHPS.
    Affected if The device is any of these six models.
  2. Check the firmware version
    Log into the web panel and navigate to the System > Firmware or Status page to view the installed firmware version. Alternatively, use SNMP or check the device documentation for the version location.
    Affected if The firmware version is lower than 4.0.10.
  3. Verify SNMP service status
    Access the web panel configuration and locate the SNMP settings (usually under Network or Services). Check if the SNMP daemon is enabled and running.
    Affected if SNMP is enabled and accessible on the network.
  4. Confirm SNMP version in use
    In the SNMP configuration page, verify which SNMP version is configured. Look for SNMPv2c or community string settings.
    Affected if SNMPv2c is configured with a community string (read/write community string is exposed in this mode).

If the device is a WP 6xxx model with firmware below 4.0.10 and SNMPv2 is enabled, the device is vulnerable to unauthenticated SNMP community string exposure.

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 the WP 6xxx firmware to version 4.0.10 or later. If immediate patching is not feasible, restrict network access to the affected devices and consider implementing SNMPv3 which supports authentication and encryption.

Recommended fix High confidence

WP 6xxx series firmware version 4.0.10

  1. Obtain firmware version 4.0.10 or later for your specific WP 6xxx model from the official PHOENIX CONTACT website or support portal
  2. Review the firmware upgrade documentation provided by PHOENIX CONTACT for your specific device model
  3. Backup the current device configuration before initiating the firmware update
  4. Upload and install the new firmware version 4.0.10 or later via the device's web-based management interface or appropriate provisioning tool
  5. After upgrade, verify that the firmware version has been successfully updated to 4.0.10 or later
  6. Test SNMPv2 functionality to confirm the vulnerability is remediated and the service operates normally
Caveat Review release notes for any configuration or feature changes between your current version and 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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