CVE-2025-22388: An issue was discovered in Optimizely EPiServer.CMS.Core before 12.22.0

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

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

Q: Is CVE-2025-22388 being exploited?

CVE-2025-22388 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-22388 affect?

CVE-2025-22388 affects optimizely cms. Severity is medium (CVSS 5.7). An issue was discovered in Optimizely EPiServer.CMS.Core before 12.22.0. A high-severity Stored Cross-Site Scripting (XSS) vulnerability exists in the CMS, allowing malicious actors to inject and execute arbitrary JavaScript code, potential

Q: How urgent is CVE-2025-22388?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 5.7UPGRADE

CVE-2025-22388 is a medium-severity flaw (CVSS 5.7) 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.22.0. A high-severity Stored Cross-Site Scripting (XSS) vulnerability exists in the CMS, allowing malicious actors to inject and execute arbitrary JavaScript code, potentially compromising user data, escalating privileges, or executing unauthorized actions. The issue exists in multiple areas, including content editing, link management, and file uploads.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.7 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 69%)
CISA exploited list	No
Weakness	CWE-79
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.22.0

Fixed in: 12.22.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.22.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-22388?

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

Is CVE-2025-22388 being exploited?

CVE-2025-22388 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-22388 affect?

CVE-2025-22388 affects optimizely cms. Severity is medium (CVSS 5.7). An issue was discovered in Optimizely EPiServer.CMS.Core before 12.22.0. A high-severity Stored Cross-Site Scripting (XSS) vulnerability exists in the CMS, allowing malicious actors to inject and execute arbitrary JavaScript code, potential

How urgent is CVE-2025-22388?

Priority 28/100. No elevated risk signals yet.

Related CVEs

CVE-2025-22390 HIGH 7.5 UPGRADE An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0
CVE-2025-22389 HIGH 8.0 UPGRADE An issue was discovered in Optimizely EPiServer.CMS.Core before 12.32.0

References

← Back to latest CVEs