# CVE-2025-11843: Auth bypass in Therefore Online and Therefore On-Premises

> Attackers can impersonate service accounts to access stored documents, requiring a patch for Therefore Online and On-Premises.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2025
- **Updated:** 31 Oct 2025
- **Also known as:** GHSA-j67p-5mwc-frf9

## What is CVE-2025-11843?

CVE-2025-11843 is a high-severity authentication bypass vulnerability in Therefore Online and Therefore On-Premises, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Therefore Corporation GmbH has recently become aware that Therefore™ Online and Therefore™ On-Premises contain an account impersonation vulnerability. A malicious user may potentially be able to impersonate the web service account or the account of a service using the API when connecting to the Therefore™ Server. If the malicious user gains this impersonation user access, then it is possible for them to access the documents stored in Therefore™. This impersonation is at application level (Therefore access level), not the operating system level.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2025-11843?


## How do I fix CVE-2025-11843?

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

## Is CVE-2025-11843 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11843 and fix it if it is affected.

What it is: CVE-2025-11843 is a high-severity authentication bypass vulnerability in Therefore Online and Therefore On-Premises, published on 31 Oct 2025. 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-2025-11843 in the wild and no public exploit code.

Affected product: Therefore Online and Therefore On-Premises. 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-2025-11843/ (Markdown: https://insights.sbomify.com/CVE-2025-11843/index.md)
```

## Sources

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

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