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

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-pr28-mf3q-qpg6

## 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 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-45012?

2 open source packages ship an affected version, including apostrophe.


| Package | Ecosystem | 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.

## Is CVE-2026-45012 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45012 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45012 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45012 exists.

Affected packages and fixed versions:
- apostrophe (npm): affected all versions up to 4.29.0; no fix listed
- apostrophe (npm): affected all versions up to 4.29.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45012/ (Markdown: https://insights.sbomify.com/CVE-2026-45012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45012
- OSV: https://osv.dev/vulnerability/CVE-2026-45012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45012/
Summaries are generated and may contain mistakes; the official description above is the record.