CVE-2023-37857
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 with admin privileges is able to read hardcoded cryptographic keys allowing the attacker to create valid session cookies. These session-cookies created by the attacker are not sufficient to obtain a valid session on 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 prior to version 4.0.10 contain hardcoded cryptographic keys that can be read by an authenticated attacker with admin privileges. The attacker can craft session cookies using these keys, though the vendor explicitly notes these forged cookies are insufficient to establish valid device sessions, limiting practical exploitation.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 WP 6xxx modelLocate the device model identifier on the physical device label or in the web panel system information. Confirm it is one of: WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215.Affected if The device is any of these six models and the firmware is below version 4.0.10.
-
Check firmware versionAccess the web panel admin interface and navigate to the firmware or system information section. Alternatively, use the device's command-line interface or management console to retrieve the firmware version string.Affected if The installed firmware version is lower than 4.0.10.
-
Confirm admin privilege access existsVerify whether admin-level credentials are configured or whether unauthorized admin accounts may exist. Check the user management or account settings in the web panel.Affected if Admin privileges are available to any user, since the vulnerability requires an authenticated attacker with admin privileges to read the hardcoded keys.
Your environment is affected if you are running any WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215 web panel with firmware version lower than 4.0.10 and admin access is present.
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 series web panels to firmware version 4.0.10 or later to remove hardcoded cryptographic keys. Additionally, limit admin-level access and monitor for unauthorized admin accounts.
PHOENIX CONTACT WP 6xxx series firmware version 4.0.10 or later
- 1. Identify the exact WP 6xxx model (WP 6070, WP 6101, WP 6121, WP 6156, WP 6185, or WP 6215) currently deployed
- 2. Download the firmware version 4.0.10 or later from the official PHOENIX CONTACT support website (cert.vde.com or phoenixcontact.com)
- 3. Review the firmware upgrade instructions in the product manual to ensure proper procedures are followed
- 4. Back up the current device configuration if supported by the firmware upgrade process
- 5. Upload and install the firmware version 4.0.10 or later onto the affected device via the web-based management interface or appropriate update mechanism
- 6. Verify the firmware version has been successfully updated by checking the device information page
- 7. After upgrade, verify that the hardcoded credentials vulnerability is resolved by confirming the cryptographic keys are no longer accessible to admin users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37857 — 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-37857 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