# CVE-2026-12981: CAFEHAUS API <= 1.0.0 - Unauthenticated Arbitrary User Password Reset

> Unauthenticated attackers can reset any user's password, including administrators, leading to full account takeover in the CAFEHAUS API plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-3j3x-65ff-623h

## What is CVE-2026-12981?

CVE-2026-12981 is a high-severity missing authorization vulnerability in Unknown CAFEHAUS API, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CAFEHAUS API WordPress plugin through 1.0.0 does not have any authentication or authorisation when updating user passwords, allowing unauthenticated attackers to set the password of any user, including administrators, and fully take over their accounts.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-12981 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12981 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12981 is a high-severity missing authorization vulnerability in Unknown CAFEHAUS API, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12981 exists.

Affected product: Unknown CAFEHAUS API. 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-12981/ (Markdown: https://insights.sbomify.com/CVE-2026-12981/index.md)
```

## Sources

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

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