# CVE-2026-14559: Teddy Bear Customize Addon <= 1.0.5 - Unauthenticated Account Takeover

> Unauthenticated attackers can log in as any user, including administrators, by supplying only an email address due to missing password verification.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-4fpp-jjwf-mmjc

## What is CVE-2026-14559?

CVE-2026-14559 is a critical authentication bypass vulnerability in Unknown teddy-bear-customize-addon, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The teddy-bear-customize-addon WordPress plugin through 1.0.5 does not verify a user's password before authenticating them, allowing unauthenticated attackers to log in as any registered user, including administrators, by supplying only that user's email address.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-14559?


## How do I fix CVE-2026-14559?

No fix has been published for CVE-2026-14559 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14559 being exploited?

There is no known exploitation of CVE-2026-14559 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14559 and fix it if it is affected.

What it is: CVE-2026-14559 is a critical authentication bypass vulnerability in Unknown teddy-bear-customize-addon, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14559 in the wild and no public exploit code.

Affected product: Unknown teddy-bear-customize-addon. 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-14559/ (Markdown: https://insights.sbomify.com/CVE-2026-14559/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14559
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14559
- OSV: https://osv.dev/vulnerability/CVE-2026-14559

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14559/
Summaries are generated and may contain mistakes; the official description above is the record.