# CVE-2021-43447: Auth bypass in n/a

> Attackers can edit documents without authentication due to incorrect access control in the ONLYOFFICE document editor.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-v44r-r7pp-7r2w

## What is CVE-2021-43447?

CVE-2021-43447 is a high-severity authentication bypass vulnerability in n/a, published on 23 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ONLYOFFICE all versions as of 2021-11-08 is affected by Incorrect Access Control. An authentication bypass in the document editor allows attackers to edit documents without authentication.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2021-43447?

It affects 1 product.


Products: Onlyoffice Server.

## How do I fix CVE-2021-43447?

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

## Is CVE-2021-43447 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43445](https://insights.sbomify.com/CVE-2021-43445/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2021-43449](https://insights.sbomify.com/CVE-2021-43449/): Server-side request forgery in n/a (high 8.1)
- [CVE-2021-43444](https://insights.sbomify.com/CVE-2021-43444/): Weak cryptography in n/a (high 7.5)
- [CVE-2021-43446](https://insights.sbomify.com/CVE-2021-43446/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2021-43448](https://insights.sbomify.com/CVE-2021-43448/): Other in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43447 and fix it if it is affected.

What it is: CVE-2021-43447 is a high-severity authentication bypass vulnerability in n/a, published on 23 Jan 2023. 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-2021-43447 exists.

Affected product: n/a. 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-2021-43447/ (Markdown: https://insights.sbomify.com/CVE-2021-43447/index.md)
```

## Sources

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

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