CVE-2025-22390
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Optimizely EPiServer.CMS.Core CMS allows users to set passwords with a minimum length of only 6 characters, which lacks adequate complexity to resist modern attack techniques such as password spraying or offline password cracking. This affects versions prior to 12.32.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 12.32.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed EPiServer.CMS.Core versionLocate the EPiServer.CMS.Core.dll in your bin or packages folder and view its file version property, or check your NuGet packages.config / .csproj file for the installed package versionAffected if The version is lower than 12.32.0
-
Access password policy configurationLog in to the Optimizely/EPiServer CMS Admin interface and navigate to the Password Policy settings (typically under Admin > Password Policy), or inspect the episerver.framework or related configuration section in your web.config / appsettings.jsonAffected if The configured minimum password length is set to 6 or fewer characters
-
Verify password policy enforcementReview whether password complexity requirements such as uppercase, lowercase, numeric, or special character mandates are configured and enforced in the systemAffected if Password complexity requirements are minimal or disabled, allowing weak passwords
You are affected if your EPiServer.CMS.Core version is below 12.32.0 AND your password policy allows minimum lengths of 6 characters or fewer without strong complexity requirements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped12.32.0
Upgrade to EPiServer.CMS.Core version 12.32.0 or later which enforces stronger password complexity requirements, or implement stricter password policy configuration if upgrade is not immediately feasible.
12.32.0
- Backup the current Optimizely CMS database and application files before proceeding with any upgrade
- Review the Optimizely release notes for version 12.32.0 to understand changes and any prerequisites
- Update the EPiServer.CMS.Core NuGet package to version 12.32.0 or later in your project
- Deploy the updated application to a staging environment for testing
- Verify that password complexity requirements are properly enforced after the upgrade
- Deploy the verified upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22390 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data