CVE-2025-22388
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.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.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Optimizely EPiServer.CMS.Core before version 12.22.0 allows authenticated or unauthenticated attackers to inject malicious JavaScript code through multiple entry points including content editing, link management, and file uploads. This stored XSS executes in the context of other users' sessions, enabling data theft, privilege escalation, and unauthorized actions.
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.22.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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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, right-click > Properties > Details to view the File Version, or inspect your project file (packages.config, .csproj) for the EPiServer.CMS.Core package versionAffected if The version number is lower than 12.22.0
-
Verify CMS admin interface accessibilityAttempt to access the Optimizely/EPiServer admin panel (typically at /episerver/cms/admin or /util/login.aspx) with a browser request to confirm the interface is exposedAffected if The admin interface returns a login page or dashboard without requiring network-level restrictions
-
Identify exposed content editing endpointsCheck if the CMS edit mode is accessible by attempting to reach the editing interface (commonly /EPiServer/CMS/Content or /cms/edit) and verify whether anonymous or low-privileged users can access content creation/modification pathsAffected if Content editing interfaces are accessible without proper authentication restrictions or network segmentation
-
Confirm link management feature exposureInspect the CMS configuration for Link Manager or outbound URL editing features; verify if these endpoints are accessible by reviewing IIS logs or testing access to link-related admin functionsAffected if Link management functionality is enabled and reachable from the web
You are affected if your EPiServer.CMS.Core version is below 12.22.0 AND any of the CMS editing, link management, or file upload features are accessible to users (authenticated or anonymous) on your network.
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.22.0
Upgrade EPiServer.CMS.Core to version 12.22.0 or later to receive the security patch; alternatively, implement input validation and output encoding on all user-supplied content in affected areas as a compensating control.
12.22.0
- Identify current Optimizely CMS version by checking the deployed assemblies or project file references
- Review Optimizely release notes and upgrade documentation for version 12.22.0
- Create a full backup of the production database and file system
- Test the upgrade in a non-production environment first
- Upgrade Optimizely CMS packages (EPiServer.CMS.Core and related packages) to version 12.22.0 or later using NuGet or the CMS admin upgrade interface
- Run any post-upgrade migration scripts if provided in the release notes
- Verify the upgrade was successful by checking the CMS version in the admin panel
- Test the previously vulnerable areas (content editing, link management, file uploads) to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22388 — 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-22388 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