Skip to main content

ApostropheCMS CVE-2026-45011

| EUVDEUVD-2026-36567 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-05-14 https://github.com/apostrophecms/apostrophe GHSA-5f64-7vfc-rcx6
7.3
CVSS 3.1 · Vendor: https://github.com/apostrophecms/apostrophe
Share

Severity by source

Vendor (https://github.com/apostrophecms/apostrophe) PRIMARY
7.3 HIGH
AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Primary rating from Vendor (https://github.com/apostrophecms/apostrophe) · only source for this CVE.

CVSS VectorVendor: https://github.com/apostrophecms/apostrophe

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

3
Source Code Evidence Fetched
May 14, 2026 - 19:02 vuln.today
Analysis Generated
May 14, 2026 - 19:02 vuln.today
CVE Published
May 14, 2026 - 18:27 nvd
HIGH 7.3

DescriptionCVE.org

Summary

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)`

<img width="1249" height="979" alt="image" src="https://github.com/user-attachments/assets/c7f77177-1711-461d-b9bd-14292a6996d5" />

  • 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.

<img width="1267" height="1034" alt="image" src="https://github.com/user-attachments/assets/a80484b4-873a-47c1-8682-84626523008a" />

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.

Impact

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

Recommendation

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.

AnalysisAI

Stored cross-site scripting in ApostropheCMS 4.29.0 allows authenticated editors to inject arbitrary JavaScript via image widget URL fields, affecting administrators and public visitors. The vulnerability permits execution of malicious payloads when victims click crafted image links on published pages. No vendor-released patch identified at time of analysis, and CVSS 7.3 (High) reflects the authenticated nature and required user interaction, though impact on administrator sessions elevates real-world risk.

Technical ContextAI

ApostropheCMS is a Node.js-based content management system distributed via npm (pkg:npm/apostrophe). This vulnerability stems from CWE-79 (Improper Neutralization of Input During Web Page Generation) in the image widget's URL link functionality. The application fails to validate or sanitize user-supplied URLs, specifically allowing dangerous protocol schemes like 'javascript:' to persist through storage and rendering. When the widget HTML is rendered in victim browsers, the href attribute containing the javascript: scheme executes as code rather than navigating. This is a classic stored XSS pattern where malicious input survives server-side processing, database storage, and template rendering without sanitization, ultimately executing in a different user's security context.

RemediationAI

No vendor-released patch identified at time of analysis based on GitHub advisory data showing 'fixed in: None'. Organizations must implement compensating controls until official patch availability. Immediate mitigation: implement server-side URL scheme validation in image widget processing to reject javascript:, data:, vbscript:, and file: protocols while allowing only http:, https:, mailto:, and relative URLs. Apply strict Content Security Policy headers with 'unsafe-inline' removed from script-src directive to block inline JavaScript execution even if XSS payloads reach the DOM. Restrict Editor role assignment to fully trusted personnel only, and enable content approval workflows requiring Administrator review before publication if supported by the platform. Monitor the official advisory at https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-5f64-7vfc-rcx6 and npm package updates for patch release announcements. Note that CSP implementation may break legitimate inline scripts if the application relies on them, requiring script refactoring. URL validation must occur server-side before database persistence, not just client-side, to prevent bypasses.

Share

CVE-2026-45011 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy