CVE-2023-26239
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 · uneditedAn issue was discovered in WatchGuard EPDR 8.0.21.0002. Due to a weak implementation of a password check, it is possible to obtain credentials to access the management console as a non-privileged user.
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 confidenceWatchGuard EPDR 8.0.21.0002 contains a weak password check implementation that allows a non-privileged user to obtain credentials and access the management console, effectively bypassing authentication controls.
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< 8.00.22.0010< 8.00.22.0010< 8.00.22.0010< 8.00.22.0010CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed WatchGuard EPDR/EPP/EDR firmware versionAccess the management console or use the product's system information interface to determine the current firmware versionAffected if The installed version is earlier than 8.00.22.0010
-
Confirm product type matches vulnerable variantsVerify that the installed product is one of: WatchGuard EPP Firmware, WatchGuard EDR Firmware, WatchGuard Epdr Firmware, or WatchGuard Panda Ad360 FirmwareAffected if The product is any of these four variants with version < 8.00.22.0010
-
Determine if management console is exposedCheck whether the WatchGuard management console interface is accessible over the network or locallyAffected if The management console is accessible and the version is < 8.00.22.0010, the weak password check flaw may be exploitable
A user is affected if their WatchGuard EPDR/EPP/EDR or Panda Ad360 installation shows a firmware version lower than 8.00.22.0010.
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 · scoped8.00.22.0010
Apply the vendor-supplied patch or update to a patched version of WatchGuard EPDR that addresses the weak password check vulnerability.
8.00.22.0010
- Verify current firmware version of the WatchGuard EPDR/Edr/Epdr or Panda Ad360 installation
- Download firmware version 8.00.22.0010 or later from the official WatchGuard support portal
- Follow vendor documentation for applying the firmware update
- Restart services if required by the update process
- Verify the upgrade was successful by checking the firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26239 — 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-26239 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