CVE-2026-14356: FleekDash V2 (WordPress plugin) · Missing Authorization
Affects FleekDash V2 (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 29 Oct 2026, 14:41 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| fleekdashFleekDash V2 | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict access to the /wp-json/fleekdash/v1/register endpoint if possible, and monitor for suspicious account creation activity. Avoid granting subscriber-level access to untrusted users. Follow updates from the FleekDash vendor for an official patch or temporary mitigation.
Description
FleekDash V2 WordPress plugin versions up to 2.6.2.2 contain an authorization bypass vulnerability. This flaw allows attackers with subscriber-level access or higher to overwrite email addresses and passwords of any WordPress user, including administrators, leading to full account takeover and site compromise. Additionally, an unauthenticated attacker can self-provision a subscriber account via a public REST endpoint, bypassing registration restrictions.