CVE-2023-37861
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 an authenticated remote attacker can execute code with root permissions with a specially crafted HTTP POST when uploading a certificate 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 confidencePHOENIX CONTACT WP 6xxx series web panels versions prior to 4.0.10 contain an authenticated remote code execution vulnerability. An authenticated attacker can execute arbitrary code with root privileges by sending a specially crafted HTTP POST request during certificate upload functionality.
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 web panel modelLocate the model number label on the physical device or check the device documentation/web interface system info. Confirm it is one of: WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215.Affected if The model is one of the six listed variants.
-
Check the installed firmware versionAccess the web panel management interface and navigate to the System or About section to view the firmware version. Alternatively, use the device's command-line interface or API if available to retrieve the firmware version.Affected if The firmware version is below 4.0.10 (for example, 4.0.9, 4.0.0, or any version number less than 4.0.10).
-
Verify the web interface is accessibleAttempt to reach the web panel HTTP/HTTPS interface from a network-connected device. Confirm the management portal is reachable and responds.Affected if The web management interface is exposed and reachable on the network.
-
Confirm certificate upload functionality is availableLog into the web panel interface and navigate to the SSL/TLS or certificate management section where certificates can be uploaded. Check if a certificate upload or import feature exists and is accessible.Affected if The certificate upload feature is present and accessible in the web interface.
-
Check authentication status on the web panelVerify whether authentication is required to access the management interface and whether the default credentials have been changed. Attempt to determine if an authenticated session can be obtained.Affected if An attacker can obtain valid authentication credentials to access the device.
A user is affected if they have a WP 6xxx series model (6070/6101/6121/6156/6185/6215) running firmware prior to 4.0.10 with the web interface and certificate upload feature accessible, regardless of authentication status since the requirement is having valid credentials which an attacker may obtain.
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 PHOENIX CONTACT WP 6xxx series web panels to firmware version 4.0.10 or later to patch the vulnerability. If immediate patching is not possible, restrict network access to the web panel management interface to trusted users only.
Firmware version 4.0.10 or later for WP 6xxx series (WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, WP 6215)
- Identify the exact model number (WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215) of the affected Phoenix Contact device
- Check the current firmware version by accessing the device's web interface or using the vendor's management tools
- Navigate to the official Phoenix Contact support page or cert.vde.com to download firmware version 4.0.10 or later for your specific model
- Follow the vendor's documented firmware upgrade procedure, typically via the web interface under System > Firmware Update or similar path
- After uploading the certificate file, ensure the upgrade process completes successfully without errors
- Restart the device if required by the upgrade procedure
- Verify the firmware has been updated to version 4.0.10 or later by checking the device status
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37861 — 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-37861 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