LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24359: WordPress Dokan plugin <= 4.2.4 - Broken Authentication vulnerability

Authentication Bypass Using an Alternate Path or Channel vulnerability in Dokan, Inc. Dokan dokan-lite allows Authentication Abuse.This issue affects Dokan: from n/a through <= 4.2.4.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24359 is a high-severity broken authentication issue in the WordPress Dokan plugin through version 4.2.4. A low-privileged logged-in user could bypass intended authentication checks, potentially impacting confidentiality, integrity, and availability. No provided source confirms active exploitation.

Executive priority

Prioritize remediation for any public WordPress site using Dokan through 4.2.4, especially where untrusted users can create accounts. The issue has high potential business impact, but current public evidence in the bundle does not show active exploitation.

Technical view

The CVE describes CWE-288, Authentication Bypass Using an Alternate Path or Channel, in Dokan dokan-lite through <= 4.2.4. CVSS 3.1 is 8.8: network exploitable, low complexity, low privileges required, no user interaction, with high CIA impact.

Likely exposure

Exposure is likely limited to WordPress installations running Dokan/dokan-lite version 4.2.4 or earlier. Sites without this plugin, or running versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates exploitation can occur remotely over the network by an authenticated low-privileged user without user interaction. The source bundle does not include exploit details, proof-of-concept status, or evidence of active exploitation; KEV status is false.

Researcher notes

The public data is sparse: CVE metadata, CVSS, CWE-288, affected range, and a Patchstack database reference. Do not assume unauthenticated exploitation; CVSS states PR:L. Validate against vendor/Patchstack updates before declaring a fixed version.

Mitigation direction

  • Inventory WordPress sites for Dokan or dokan-lite installations.
  • Identify installed Dokan plugin versions and prioritize <= 4.2.4.
  • Check Dokan and Patchstack guidance for the fixed version or official mitigation.
  • Update the plugin if an official fixed release is available.
  • Restrict unnecessary user registration or low-privilege accounts until remediated.
  • Increase monitoring of authentication and privilege-related events.

Validation and detection

  • Confirm whether Dokan/dokan-lite is installed on each WordPress site.
  • Record the installed plugin version and compare against <= 4.2.4.
  • Verify remediation status against vendor or Patchstack advisory updates.
  • Review recent logs for unusual authenticated activity or privilege changes.
  • After updating, confirm the deployed version is no longer affected.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24359 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-24359Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Dokan, Inc.Dokandokan-lite, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.