Apostrophe has stored XSS via javascript: URL in Image Widget Link

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-45011: 0.27% estimated exploitation activity in the next 30 days; percentile 18.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

14 May 2026, 18:27 UTC

Last modified by the source

12 Jun 2026, 22:15 UTC

Source last checked

26 Oct 2026, 12:55 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5f64-7vfc-rcx6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5f64-7vfc-rcx6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45011

Advisory: Apostrophe has stored XSS via javascript: URL in Image Widget Link
IDs: CVE-2026-45011, GHSA-5f64-7vfc-rcx6
Record: https://patchnext.com/advisories/cve-2026-45011 (revision 2, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm apostrophe: affected >= 4.29.0, <= 4.29.0

## Suggested inspection (read-only)
- `npm ls apostrophe --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on apostrophe.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5f64-7vfc-rcx6 (OSV record GHSA-5f64-7vfc-rcx6 lists affected ranges: npm apostrophe >=4.29.0 <=4.29.0)
- Verified: https://github.com/advisories/GHSA-5f64-7vfc-rcx6 (GitHub-reviewed advisory GHSA-5f64-7vfc-rcx6 lists affected ranges: npm apostrophe >=4.29.0 <=4.29.0)

Commands are suggestions: review each one before running it.