CVE-2026-45011

A stored cross-site scripting vulnerability was identified in the image widget functionality. A user with the Editor role can configure an image widget link to use a javascript: URL payload.

Because editors have permission to publish pages, the malicious widget can be published to the live site. When another user, including an administrator or public visitor, clicks the affected image/link, arbitrary JavaScript executes in the victim’s browser.

Affected Version

ApostropheCMS (tested on version: v4.29.0)

Steps to Reproduce

Precondition
Ensure at least one image exists in the media library.

If the media library is empty:

• Log in as an Editor.
• Open the media library.
• Upload any JPG or PNG image.
• Set any title, for example Probe image.
• Publish the image and close the media manager.

Exploitation Steps

• Log in as an Editor.
• Open the home page.
• Enable edit mode for the page.
• In the main content area, click Add content.
• Select the Image widget.
• Choose any existing image from the image picker and save/select it.
• Open the image widget settings.
• Locate the Link to field and change it to URL.
• In the URL field, enter: javascript:alert(document.domain)

• Save the image and click on Update.
• As another user, such as an administrator or guest, open the published page and click the linked image.
• Observe that the JavaScript payload executes.

Note: This attack can also be performed by a Contributor. However, because contributors cannot publish content directly, the malicious image widget remains in the draft version and is only visible to users with access to review drafts, such as administrators or editors.

If an administrator reviews and approves/publishes the affected draft, the stored XSS becomes part of the live page and can then affect all users who interact with the malicious image link.

Successful exploitation allows an Editor to store a JavaScript payload in published page content. When a victim clicks the affected image link, the payload executes in the victim’s browser.

This may allow an attacker to:

• perform actions in the context of an authenticated administrator
• access sensitive information available in the CMS interface
• modify page content or configuration
• conduct phishing attacks within the trusted site
• compromise visitors who interact with the published image link

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-45011 has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

Validate and sanitize all user-supplied URLs used in widget link fields.

Specifically:

• Reject dangerous URL schemes such as javascript:, data:, and other executable schemes.
• Allow only safe protocols such as http:, https:, mailto:, and relative URLs where appropriate.
• Normalize and validate URLs server-side before storage.
• Encode rendered URLs safely in templates.
• Consider applying a strict Content Security Policy to reduce the impact of XSS.

1. What is CVE-2026-45011? CVE-2026-45011 is a high-severity cross-site scripting (XSS) vulnerability in apostrophe (npm), affecting versions = 4.29.0. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-45011? CVE-2026-45011 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of apostrophe are affected by CVE-2026-45011? apostrophe (npm) versions = 4.29.0 is affected.
4. Is there a fix for CVE-2026-45011? No fixed version is listed for CVE-2026-45011 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-45011 exploitable, and should I be worried? Whether CVE-2026-45011 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-45011 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-45011? No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.