CVE-2023-3572
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, unauthenticated attacker may use an attribute of a specific HTTP POST request releated to date/time 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 confidenceThe WP 6xxx series web panels from PHOENIX CONTACT contain a critical vulnerability in versions prior to 4.0.10. An unauthenticated remote attacker can exploit a specific HTTP POST request attribute related to date/time operations to gain full administrative access to the device. The CVSS 10 score indicates trivial exploitability with complete compromise of confidentiality, integrity, and availability.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 device management interface and look for the model designation (WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215) in the header, footer, or system information pageAffected if The device is one of the WP 6xxx series models listed in the affected products
-
Check the firmware versionNavigate to the web panel system settings, about page, or firmware information section. The version number is typically displayed as a four-part number (such as 4.0.9 or 4.0.10)Affected if The displayed firmware version is less than 4.0.10 (for example, 4.0.9, 4.0.8, 3.x.x, etc.)
-
Verify web panel accessibilityConfirm the web management interface (HTTP/HTTPS on port 80 or 443) is reachable from the network by attempting to access the device IP in a browserAffected if The web panel is exposed and accessible on the network
-
Confirm date/time feature is in useThe vulnerability is triggered via a specific HTTP POST request attribute related to date/time operations. Check if the web panel has date/time configuration enabled in system settingsAffected if The date/time configuration feature is accessible or enabled on the device
The device is affected if it is a WP 6xxx model running firmware version prior to 4.0.10 and has its web panel interface accessible on the network.
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
Upgrade PHOENIX CONTACT WP 6xxx web panels to firmware version 4.0.10 or later. If immediate patching is not feasible, restrict network access to the web panel management interface using network segmentation and firewall rules.
Firmware 4.0.10 or later for WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, and WP 6215
- Identify the specific WP 6xxx model number (6070, 6101, 6121, 6156, 6185, or 6215) from the affected device
- Check the current firmware version running on the device through the web interface or administrative console
- Navigate to the official PHOENIX CONTACT support page or download portal to obtain firmware version 4.0.10 or later for your specific model
- Follow the vendor's documented firmware update procedure, typically accessible through the device's web-based management interface
- After uploading and applying the firmware update, wait for the device to reboot and complete the installation process
- Verify the new firmware version is 4.0.10 or higher by checking the device management interface
- Confirm the HTTP POST endpoint related to date/time operations no longer accepts injectable parameters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3572 — 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-3572 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