# CVE-2025-22390: Weak cryptography in n/a

> Optimizely CMS allows weak passwords with only 6 characters, facilitating account takeover via password spraying or cracking.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 4 Jan 2025
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-f4vp-28x5-837r

## What is CVE-2025-22390?

CVE-2025-22390 is a high-severity vulnerability in n/a, published on 4 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0. A medium-severity vulnerability exists in the CMS due to insufficient enforcement of password complexity requirements. The application permits users to set passwords with a minimum length of 6 characters, lacking adequate complexity to resist modern attack techniques such as password spraying or offline password cracking.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Optimizely Optimizely Cms.

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

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

## Is CVE-2025-22390 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-22389](https://insights.sbomify.com/CVE-2025-22389/): File upload in n/a (high 8.0)
- [CVE-2025-22388](https://insights.sbomify.com/CVE-2025-22388/): Cross-site scripting in n/a (medium 5.7)
- [CVE-2023-31754](https://insights.sbomify.com/CVE-2023-31754/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22390 is a high-severity vulnerability in n/a, published on 4 Jan 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-22390 in the wild and no public exploit code.

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-2025-22390/ (Markdown: https://insights.sbomify.com/CVE-2025-22390/index.md)
```

## Sources

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

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