dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-45011

HIGH · 7.3 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable

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 · unedited
ApostropheCMS is an open-source Node.js content management system. Version 4.29.0 has a stored cross-site scripting vulnerability 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. As of time of publication, no known patched versions are available.

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 confidence

ApostropheCMS 4.29.0 contains a stored XSS vulnerability in its image widget link functionality. Users with Editor role can configure an image widget link using a javascript: URL payload, which gets stored and published to the live site. When victims click the affected image/link, arbitrary JavaScript executes in their browser.

MitigationSince no patch is available, implement input validation to reject javascript: and other dangerous protocols in URL fields. Consider temporarily disabling custom link functionality in image widgets or adding Content-Security-Policy headers as a defense-in-depth measure until an official patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ApostropheCMS version
    Check the package.json file in your ApostropheCMS installation directory for the version field, or run `npm list apostrophe` if npm is available. Alternatively, check the admin UI dashboard for the CMS version.
    Affected if The installed version is 4.29.0 or falls within the affected range around this version.
  2. Confirm image widget is in use
    Navigate to the ApostropheCMS admin panel and examine your page builder or content editor. Look for pages or pieces that utilize the image widget, which is a standard widget type in ApostropheCMS.
    Affected if Image widgets are actively used in your site's content.
  3. Verify Editor role permissions
    In the ApostropheCMS admin UI, go to the Users or Roles management section and confirm that users with the Editor role exist and have permission to edit content containing image widgets.
    Affected if Editor role users exist and can edit content with image widgets.
  4. Inspect stored image widget links for malicious protocols
    Query your database for image widget documents that contain link fields. Search for entries where the link URL starts with 'javascript:' or other potentially dangerous protocols. The exact query depends on your database (MongoDB by default), but look in the appropriate widget or page collection for fields like 'linkUrl' or similar.
    Affected if Any image widget in your database contains a link URL starting with 'javascript:' or other non-http(s) protocols.

You are affected if your ApostropheCMS installation is version 4.29.0 (or nearby), you use image widgets with link functionality, and your database contains any image widget link configured with a javascript: protocol URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since no patch is available, implement input validation to reject javascript: and other dangerous protocols in URL fields. Consider temporarily disabling custom link functionality in image widgets or adding Content-Security-Policy headers as a defense-in-depth measure until an official patch is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45011 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45011 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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