dbcve.org
Wp 6070 Wvps FirmwareOperating system · Phoenixcontact

CVE-2023-37862

HIGH · 8.2 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 4.0.10 or later.
See remediation →
91/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
In PHOENIX CONTACTs WP 6xxx series web panels in versions prior to 4.0.10 an unauthenticated remote attacker can access upload-functions of the HTTP API. This might cause certificate errors for SSL-connections and might result in a partial denial-of-service.

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

Unauthenticated remote attackers can access upload functions in the HTTP API of PHOENIX CONTACT WP 6xxx series web panels prior to version 4.0.10. This can cause SSL certificate errors for legitimate connections and result in partial denial-of-service conditions.

MitigationUpgrade WP 6xxx web panels to firmware version 4.0.10 or later to remediate this vulnerability. Consider network segmentation to limit exposure of the HTTP API to untrusted networks.

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
None
Integrity
High
Availability
Low

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

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 WP 6xxx model
    Check the device label, web interface, or system information to confirm the specific model: WP 6070 WVPS, WP 6101 WXPS, WP 6121 WXPS, WP 6156 WHPS, WP 6185 WHPS, or WP 6215 WHPS
    Affected if The model is any of the WP 6xxx series variants listed in the affected products
  2. Check the installed firmware version
    Access the device web panel or use the device's firmware version check function to determine the current firmware version
    Affected if The firmware version is lower than 4.0.10 (for example, 4.0.9, 4.0.8, etc.)
  3. Verify HTTP API accessibility
    Attempt to access the HTTP API endpoint on the device from an untrusted network or confirm whether the API port (typically port 80/443) is exposed to untrusted networks
    Affected if The HTTP API is accessible from untrusted networks without network segmentation or authentication barriers
  4. Confirm upload function exposure
    Check if the upload functionality in the HTTP API can be accessed without authentication by reviewing the API endpoint configuration or testing access to upload-related paths
    Affected if The upload functions in the HTTP API are reachable without authentication

You are affected if you have a WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215 device running firmware version below 4.0.10 with an exposed HTTP API.

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 WP 6xxx web panels to firmware version 4.0.10 or later to remediate this vulnerability. Consider network segmentation to limit exposure of the HTTP API to untrusted networks.

Recommended fix High confidence

Firmware version 4.0.10 or later for WP 6xxx series (WP 6070, 6101, 6121, 6156, 6185, 6215)

  1. Identify the exact model number (WP 6070, 6101, 6121, 6156, 6185, or 6215) of the affected Phoenix Contact web panel
  2. Check the current firmware version installed on the device through its web interface or administrative 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. Before upgrading, review the firmware release notes for any special upgrade instructions or prerequisites
  5. Upload and install the new firmware through the device's web-based administration interface or using the manufacturer's recommended upgrade procedure
  6. After the firmware upgrade completes, verify the new version is installed correctly
  7. Confirm the HTTP API upload functions now require proper authentication
  8. Test that SSL certificate handling operates correctly
Caveat Review release notes for any configuration changes or compatibility considerations before upgrading

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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