CVE-2023-3571
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 POST releated to certificate operations 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 · moderate confidenceA privilege escalation vulnerability in PHOENIX CONTACT WP 6xxx web panels allows remote attackers with low-privilege credentials to gain full administrative access via a specific HTTP POST request related to certificate operations. This authentication bypass in versions prior to 4.0.10 enables complete device compromise.
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 web panel login page or system information page and note the model designation (WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215). This is typically displayed on the login screen or in the System > Information section.Affected if The device model is any of the following: WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215.
-
Check the installed firmware versionIn the web panel interface, navigate to System > Firmware or System > Information to view the current firmware version number. Compare it to the affected version range.Affected if The firmware version is below 4.0.10.
-
Verify web panel network accessibilityAttempt to access the web panel HTTP/HTTPS ports from an external network segment or use a network scanner to confirm the device web interface is reachable on ports 80/443 (or configured custom ports).Affected if The web panel is accessible from network segments outside the trusted administrative zone.
-
Confirm presence of low-privilege accountsCheck if any non-administrative user accounts are configured in the web panel under User Management or Access Control settings.Affected if Low-privilege user accounts exist in the device user database.
The device is affected if it is a WP 6xxx model (6070/6101/6121/6156/6185/6215) running firmware version below 4.0.10, has its web panel network-accessible, and contains at least one low-privilege user account that could be exploited for privilege escalation via the certificate operations HTTP POST endpoint.
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 WP 6xxx devices to firmware version 4.0.10 or later. Until patched, restrict network access to the web panel interface using firewall rules or network segmentation to minimize exposure.
Firmware 4.0.10 (or later) for WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, WP 6215 series
- 1. Back up the current device configuration before initiating the upgrade
- 2. Obtain firmware version 4.0.10 or later from the PHOENIX CONTACT support website (cert.vde.com or official Phoenix Contact support channels)
- 3. Log in to the WP 6xxx web panel with administrative credentials
- 4. Navigate to the firmware upgrade or system maintenance section of the web interface
- 5. Upload the firmware file (version 4.0.10 or later) and initiate the upgrade process
- 6. Wait for the upgrade to complete and the device to reboot
- 7. Verify the device is running firmware version 4.0.10 or later by checking the system information
- 8. Restore the previously backed up configuration if needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3571 — 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-3571 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