CVE-2023-3573
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 command injection in a HTTP POST request releated to font configuration 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 · high confidenceA command injection vulnerability in PHOENIX CONTACT WP 6xxx series web panels (versions prior to 4.0.10) allows remote authenticated attackers with low privileges to execute arbitrary commands via specially crafted HTTP POST requests related to font configuration operations, potentially gaining full device access.
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 or check the physical device label to confirm it is a PHOENIX CONTACT WP series model (WP 6070 WVPS, WP 6101 WXPS, WP 6121 WXPS, WP 6156 WHPS, WP 6185 WHPS, or WP 6215 WHPS).Affected if The device is one of the listed WP 6xxx models.
-
Check the firmware versionLog into the web panel interface and navigate to System Information or Device Status page to view the installed firmware version. Alternatively, check via the device's administration console or startup logs.Affected if The firmware version is lower than 4.0.10.
-
Verify web panel HTTP service is enabledAttempt to access the device's web interface via HTTP (port 80) or HTTPS (port 443) from a network-connected host. Confirm the web service responds.Affected if The web panel HTTP/HTTPS service is accessible on the network.
-
Confirm font configuration feature is accessibleLocate the font configuration or font management section within the web panel's settings menu. Check if unauthenticated or low-privilege authenticated users can access font upload or font configuration operations.Affected if Font configuration operations are available to authenticated users with low privileges.
The device is affected if it is a PHOENIX CONTACT WP 6xxx model with firmware version below 4.0.10 and the web panel interface with font configuration features is network-accessible.
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 series web panels to version 4.0.10 or later to remediate this vulnerability. Restrict network access to the web panel interface as an interim compensating control.
Firmware 4.0.10 or later for WP 6xxx series (WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, WP 6215)
- Identify the specific WP 6xxx model (WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215) from the device label or web interface
- Access the device's web-based management interface and navigate to the firmware/version information section
- Verify the current firmware version is below 4.0.10
- Obtain the firmware version 4.0.10 or later from the official PHOENIX CONTACT support website (cert.vde.com or phoenixcontact.com)
- Follow the manufacturer's documented firmware update procedure to upload and install the new firmware version
- After upgrade, verify the firmware version shows 4.0.10 or later in the web interface
- Confirm the font configuration functionality works properly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3573 — 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-3573 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