CVE-2026-45012 Apostrophe has authenticated SSRF in rich-text widget import via @apostrophecms/area/validate-widget
Authenticated attackers can trigger server-side requests to internal or external URLs via rich-text widget imports, potentially exfiltrating data or executing code.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-45012?
CVE-2026-45012 is a high-severity server-side request forgery vulnerability in apostrophecms apostrophe, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
ApostropheCMS is an open-source Node.js content management system. Versions up to and including 4.29.0 contain an authenticated server-side request forgery (SSRF) in the rich-text widget import flow. An authenticated user who can submit/edit rich-text widget content can cause the server to fetch attacker-controlled URLs during widget validation. For image-compatible responses, the fetched content can be persisted and re-hosted by Apostrophe, allowing response exfiltration. As of time of publication, no known patched versions are available.
Weakness: CWE-918
Which versions are affected by CVE-2026-45012?
2 open source packages ship an affected version, including apostrophe.
| Package | Affected | Fixed in |
|---|---|---|
apostrophe npm | All versions to 4.29.0 | None |
apostrophe npm | All versions to 4.29.0 | None |
How do I fix CVE-2026-45012?
No fix has been published for CVE-2026-45012 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-45012 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45012 exists.
Sources
Also known as GHSA-pr28-mf3q-qpg6.