CVE-2026-66677 WordPress Leyka plugin <= 3.32.3 - Broken Authentication vulnerability
High 7.6
Published
Updated
Check this codebase for CVE-2026-66677 and fix it if it is affected.
What it is: CVE-2026-66677 is a high-severity authentication bypass vulnerability in VaultDweller Leyka, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66677 in the wild and no public exploit code.
Affected product: VaultDweller Leyka. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-66677/ (Markdown: https://insights.sbomify.com/CVE-2026-66677/index.md)
Attackers can bypass authentication to gain subscriber privileges in the Leyka WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-66677?
CVE-2026-66677 is a high-severity authentication bypass vulnerability in VaultDweller Leyka, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Subscriber Broken Authentication in Leyka <= 3.32.3 versions.
Weakness: CWE-288
Which versions are affected by CVE-2026-66677?
How do I fix CVE-2026-66677?
No fix has been published for CVE-2026-66677 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-66677 being exploited?
There is no known exploitation of CVE-2026-66677 in the wild and no public exploit code.
Sources
Also known as GHSA-96rh-xvcc-h6fr.