CVE-2025-22389: An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0

Q: How do I fix CVE-2025-22389?

optimizely cms: upgrade to 12.32.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-22389 being exploited?

CVE-2025-22389 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-22389 affect?

CVE-2025-22389 affects optimizely cms. Severity is high (CVSS 8.0). An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0. A medium-severity vulnerability exists in the CMS, where the application does not properly validate uploaded files. This allows the upload of potentially malicious fil

Routine

HIGH 8.0UPGRADE

CVE-2025-22389 is a high-severity flaw (CVSS 8.0) affecting optimizely cms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0. A medium-severity vulnerability exists in the CMS, where the application does not properly validate uploaded files. This allows the upload of potentially malicious file types, including .docm .html. When accessed by application users, these files can be used to execute malicious actions or compromise users' systems.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.0 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Weakness	CWE-434
Published	2025-01-04
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: optimizely

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-01-04 02:15 UTCPublished CVE record published
2026-06-17 08:46 UTCUpdated Record last modified

optimizely optimizely cms UPGRADE

Affected: < 12.32.0

Fixed in: 12.32.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy optimizely-cms || rpm -q optimizely-cms || optimizely-cms --version

2. UPGRADE to 12.32.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade optimizely-cms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade optimizely-cms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-22389?

optimizely cms: upgrade to 12.32.0. Exact commands for each OS are on this page.

Is CVE-2025-22389 being exploited?

CVE-2025-22389 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-22389 affect?

CVE-2025-22389 affects optimizely cms. Severity is high (CVSS 8.0). An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0. A medium-severity vulnerability exists in the CMS, where the application does not properly validate uploaded files. This allows the upload of potentially malicious fil

How urgent is CVE-2025-22389?

Priority 39/100. High severity

Related CVEs

CVE-2025-22390 HIGH 7.5 UPGRADE An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0
CVE-2025-22388 MEDIUM 5.7 UPGRADE An issue was discovered in Optimizely EPiServer.CMS.Core before 12.22.0

References

← Back to latest CVEs