CVE-2026-66677

Leyka <= 3.32.3 - Missing Authorization

2026-08-19 00:00
Jakub Herman

Strategic Overview

Status
Unpatched
Affected Plugin
Leyka
Affected Version
<= 3.32.3
CVSS
4.3Medium
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2026-66677
View all Leyka vulnerabilities

At a glance

CVE-2026-66677 is a medium-severity Improper Authentication vulnerability in the Leyka WordPress plugin, affecting versions <= 3.32.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Jakub Herman.

Vulnerability Overview

The Leyka plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 3.32.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-287: Improper Authentication

Reaching this weakness in Leyka <= 3.32.3 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. No fixed build of this plugin is recorded for Leyka yet, so installs running <= 3.32.3 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C