# CVE-2026-113616: LogixFast Auth < 1.0.4 - Unauthenticated Account Takeover via Password Reset


- **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
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-xjfv-965p-5j67

## What is CVE-2026-113616?

CVE-2026-113616 is a critical vulnerability in Unknown LogixFast Auth, published on 29 Oct 2026. 

### Official description

The LogixFast Auth WordPress plugin before 1.0.4 does not deliver its password-reset one-time code to the resolved account's own email address, mailing it to the address supplied in the request instead, allowing unauthenticated attackers to reset any user's password, including an administrator's, and take over the account.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-113616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113616 is a critical vulnerability in Unknown LogixFast Auth, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113616 in the wild and no public exploit code.

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

## Sources

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

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