# CVE-2022-25369: Auth bypass in n/a

> Attackers can bypass authentication to create admin accounts and upload executable files, leading to remote code execution.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-4p27-wx99-rf43

## What is CVE-2022-25369?

CVE-2022-25369 is a critical authentication bypass vulnerability in n/a, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Dynamicweb before 9.12.8. An attacker can add a new administrator user without authentication. This flaw exists due to a logic issue when determining if the setup phases of the product can be run again. Once an attacker is authenticated as the new admin user they have added, it is possible to upload an executable file and achieve command execution. This is fixed in 9.5.9, 9.6.16, 9.7.8, 9.8.11, 9.9.8, 9.10.18, 9.12.8, and 9.13.0 (and later).

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-25369?


## How do I fix CVE-2022-25369?

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

## Is CVE-2022-25369 being exploited?

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

Public exploit code:

- Dynamicweb 9.5.0 - 9.12.7 Unauthenticated Admin User Creation (nuclei): http/cves/2022/CVE-2022-25369.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25369 and fix it if it is affected.

What it is: CVE-2022-25369 is a critical authentication bypass vulnerability in n/a, published on 23 Jan 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-2022-25369 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-2022-25369/ (Markdown: https://insights.sbomify.com/CVE-2022-25369/index.md)
```

## Sources

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

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