CVE-2025-22390VulnerabilityPublished 4 Jan 2025Updated 6 Jan 2025

CVE-2025-22390: episerver.cms.core · Weak Password Requirements

Affects episerver.cms.coreSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 12.32.0 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 12.32.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Optimizely/episerver.cms.core to 12.32.0.

Affected software

Product	Affected	Fixed in
NuGetOptimizely/episerver.cms.core`pkg:nuget/Optimizely/episerver.cms.core`Other threats	Affected <12.32.0	Fixed in 12.32.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately assess their use of Optimizely EPiServer.CMS.Core and upgrade to version 12.32.0 or later, where password complexity enforcement is improved. In the absence of an available patch, administrators should implement compensating controls such as enforcing stronger password policies via custom configuration or integration with external authentication providers that mandate complexity and length requirements. Deploying multi-factor authentication (MFA) is critical to reduce the risk of account compromise even if weak passwords are used. Monitoring authentication logs for unusual login attempts, such as repeated failed logins indicative of password spraying, can help detect exploitation attempts early. Additionally, organizations should educate users on creating strong passwords and consider implementing account lockout policies after multiple failed attempts to hinder brute-force attacks. Regular security audits and penetration testing focusing on authentication mechanisms will help identify residual weaknesses.

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.

Impact

The primary impact of this vulnerability is unauthorized access due to weak password policies, which can lead to confidentiality breaches. Attackers exploiting this flaw can gain access to user accounts, potentially including administrative accounts, allowing them to view sensitive content or manipulate CMS configurations. Although integrity and availability impacts are not directly indicated, unauthorized access could be leveraged to deface websites, inject malicious content, or disrupt services indirectly. The ease of exploitation without authentication or user interaction increases the risk of widespread attacks, especially via automated password spraying tools. Organizations worldwide using affected versions of Optimizely EPiServer.CMS.Core face increased risk of compromise, data leakage, and reputational damage. The vulnerability also raises compliance concerns for organizations subject to data protection regulations requiring strong authentication controls.

CWE-521Weak Password Requirements (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not require that users should have strong passwords.
Architecture and Design
A product's design should require adherance to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes: Enforcement of a minimum and maximum length; Restrictions against password reuse; Restrictions against using…
Architecture and Design
Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
Implementation
Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.1.2 (opens in a new tab)
V2.1.4 (opens in a new tab)
V2.1.3 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Kerberoasting (opens in a new tab)
Rainbow Table Password Cracking (opens in a new tab)
Remote Services with Stolen Credentials (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.optimizely.com/hc/en-us/articles/33182255281293-Content-Management-System-CMS-Security-Advisory-CMS-2025-02 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Feb 2026, 22:12 UTC

WeaknessesCWE-521

Technical details

References

Community reviews

Related threats