CVE-2023-3570
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 · uneditedIn PHOENIX CONTACTs WP 6xxx series web panels in versions prior to 4.0.10 a remote attacker with low privileges may use a specific HTTP DELETE 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 confidenceThe WP 6xxx series web panels from PHOENIX CONTACT contain an authentication bypass vulnerability in versions prior to 4.0.10. A remote attacker with low-privilege access can send a specific HTTP DELETE request to gain full administrative access to the device, effectively bypassing authentication controls through improper handling of the HTTP method.
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< 4.0.10< 4.0.10< 4.0.10< 4.0.10< 4.0.10< 4.0.10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web interface main page or check the physical device label to confirm it is a WP 6070 WVPS, WP 6101 WXPS, WP 6121 WXPS, WP 6156 WHPS, WP 6185 WHPS, or WP 6215 WHPS modelAffected if The device is one of the WP 6xxx series models listed in the affected products
-
Check the firmware versionLog into the device's web interface and navigate to System Information or Settings to view the installed firmware version. Compare this to version 4.0.10Affected if The installed firmware version is earlier than 4.0.10
-
Verify web interface is accessibleAttempt to reach the device's web interface over HTTP/HTTPS from the network segment where you would detect an attackAffected if The web interface is network-accessible from an untrusted network or segment
-
Check for configured user accountsReview the device's user management or account configuration to see if any user accounts are definedAffected if Any user accounts exist on the device (the vulnerability allows a low-privilege account to escalate to full administrative access)
The environment is affected if it contains a WP 6xxx series device running firmware version earlier than 4.0.10 with the web interface accessible and with at least one user account configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.0.10
Update the WP 6xxx web panel firmware to version 4.0.10 or later to patch this vulnerability. Additionally, restrict network access to the device's web interface using firewalls or network segmentation to limit exposure to untrusted networks.
Firmware 4.0.10 (WP 6xxx series)
- Obtain the firmware version 4.0.10 or later from the official PHOENIX CONTACT support portal or cert.vde.com
- Review the device backup procedures and create a backup of the current device configuration
- Transfer the firmware file to the WP 6xxx device using the vendor-recommended method (web interface, SD card, or management tool)
- Initiate the firmware upgrade following the vendor's documented upgrade procedure
- Verify the upgrade was successful by checking the firmware version in the device web interface or management console
- Confirm the device is functioning normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-3570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3570 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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