# CVE-2026-110956: asVereinbase < 1.1.8 - Unauthenticated Authentication Bypass via 2FA Validation


- **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:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-3838-5p3q-5cgw

## What is CVE-2026-110956?

CVE-2026-110956 is a critical vulnerability in Unknown asVereinbase, published on 24 Oct 2026. 

### Official description

The asVereinbase  WordPress plugin before 1.1.8 does not require a valid password or a genuine second factor before authenticating a user, treating an empty stored value as a match, so an unauthenticated attacker can log in as any user, including an administrator.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-110956 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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