CVE-2026-45012: ApostropheCMS authenticated SSRF in rich-text widget import

CVE-2026-45012 · Severity: high · CVSS 7.6 · Published 2026-06-12

ApostropheCMS, a platform used for building and managing websites, contains a security flaw in how it handles rich-text content. An authorized user, such as a content editor, can trick the server into making requests to internal systems or external websites that should be off-limits. This could allow an attacker to scan internal networks or steal sensitive images and data by forcing the server to download and re-host them.

Technologies: ApostropheCMS, apostrophe (npm). Vendors: ApostropheCMS, npm.

Quick answers

Is CVE-2026-45012 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45012 being exploited in the wild.
How severe is CVE-2026-45012?
High severity, with a CVSS score of 7.6, published 12 June 2026.
Which products and versions are affected?
ApostropheCMS <= 4.29.0; apostrophe (npm) <= 4.29.0, SEMVER:introduced=0,last_affected=4.29.0.
Is there a fix for CVE-2026-45012?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-45012 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-45012?
Check whether you run ApostropheCMS or apostrophe (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An authenticated Server-Side Request Forgery (SSRF) exists in ApostropheCMS versions <= 4.29.0. The vulnerability is located in the rich-text widget's import flow, specifically within the `@apostrophecms/area/validate-widget` endpoint. When a widget payload contains `import.html`, the backend parses `<img>` tags and uses the `fetch()` API to retrieve the source URLs. Because these URLs are not properly validated, an authenticated attacker can provide internal or restricted URLs. If the response is an image, Apostrophe persists and re-hosts the file, allowing for data exfiltration. For non-image responses, the flaw can still be used for internal port scanning and service discovery. As of the advisory date, no patched version is available.

Affected products

  • Apostrophe Technologies ApostropheCMS <= 4.29.0

Identifiers

  • CVE-2026-45012
  • GHSA-pr28-mf3q-qpg6

Timeline

  • 2026-05-13: advisory: GitHub Security Advisory published
  • 2026-06-12: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.