CVE-2026-14356
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 · uneditedThe FleekDash V2 plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.6.2.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite the email address and password of any WordPress user, including administrators, enabling full account takeover and complete site compromise. The public /wp-json/fleekdash/v1/register endpoint auto-provisions a Subscriber-role account and returns a valid REST nonce regardless of the site's users_can_register setting, enabling unauthenticated attackers to self-provision the required credentials and nonce in a single prior request.
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 confidenceThe FleekDash V2 WordPress plugin (versions up to 2.6.2.2) has an authorization bypass via the /wp-json/fleekdash/v1/register endpoint which auto-provisions Subscriber-role accounts with valid REST nonces regardless of the users_can_register setting. This enables unauthenticated attackers to obtain valid credentials, then exploit missing authorization checks to overwrite any user's email and password—including administrators—leading to complete site compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Verify FleekDash V2 plugin is installedNavigate to Plugins > Installed Plugins in WordPress admin and look for 'FleekDash V2' in the list of active pluginsAffected if The plugin is present and active in the WordPress installation
-
Check the installed plugin versionClick on the FleekDash V2 plugin to view its details, or inspect the plugin file header in wp-content/plugins/fleekdash-v2/fleekdash-v2.php to find the Version fieldAffected if The version is lower than 2.6.2.3 (e.g., 2.6.2.2, 2.6.2, 2.6.1, etc.)
-
Confirm the vulnerable REST endpoint is accessibleSend a GET request to /wp-json/fleekdash/v1/register using curl or a browser and check if it returns a valid JSON response with a nonce valueAffected if The endpoint responds with 200 OK and returns a REST nonce without requiring authentication
-
Verify if user registration is enabled on the siteGo to Settings > General in WordPress admin and check the 'Membership' setting for 'Anyone can register'Affected if Anyone can register is checked OR (regardless of this setting) the /wp-json/fleekdash/v1/register endpoint auto-provisions accounts as described in the CVE
A site is affected if the FleekDash V2 plugin is installed with a version below 2.6.2.3 and the vulnerable /wp-json/fleekdash/v1/register endpoint is accessible, allowing privilege escalation via subscriber accounts.
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.
From vendor dataUpdate FleekDash V2 to a version newer than 2.6.2.2, or disable the plugin until a patched version is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14356 — 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-2026-14356 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