CVE-2026-53607
published 2026-06-12CVE-2026-53607: ApostropheCMS is an open-source Node.js content management system. In versions up to and including 4.30.0, when `prettyUrls: true` is enabled on…
PriorityP419low3.7CVSS 3.1
AVNACHPRNUINSUCLINAN
EPSS
0.23%
13.6th percentile
ApostropheCMS is an open-source Node.js content management system. In versions up to and including 4.30.0, when `prettyUrls: true` is enabled on `@apostrophecms/file` (a documented SEO feature for serving uploaded files at clean URLs), the public pretty-URL handler builds the upstream URL using the raw `Host` HTTP request header. That URL is then `fetch`'ed and the response body + headers are streamed straight back to the requester. Because `Host` is fully attacker-controlled, an unauthenticated remote attacker can pivot the apostrophe process to issue outbound HTTP requests against any host it can reach on the private network. The path component is constrained to `/uploads/attachments/-.` (built from a local-DB lookup), which keeps the impact narrow: cross-instance data exfiltration is neutralized by cuid uniqueness, but blind-SSRF residuals remain (network-topology mapping via response-code / timing differences and verbose proxy/WAF 404 body disclosure). As of time of publication, no known patched versions exist.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apostrophecms | apostrophe | <= 4.30.0 | — |
| apostrophecms | apostrophe | >= 0 < 4.31.0 | 4.31.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
@apostrophecms/file pretty-URL Vulnerable to Unauthenticated SSRF via Host header
ghsa·2026-07-31
CVE-2026-53607 [LOW] CWE-918 @apostrophecms/file pretty-URL Vulnerable to Unauthenticated SSRF via Host header
@apostrophecms/file pretty-URL Vulnerable to Unauthenticated SSRF via Host header
### Summary
When `prettyUrls: true` is enabled on `@apostrophecms/file` (a documented SEO
feature for serving uploaded files at clean URLs), the public pretty-URL
handler builds the upstream URL using the raw `Host` HTTP request header:
```js
proxyUrl = `${req.protocol}://${req.get('host')}${uglyUrl}`
```
That URL is then `fetch`'ed and the response body + headers are streamed
straight back to the requester. Because `Host` is fully attacker-controlled,
an **unauthenticated remote** attacker can pivot the apostrophe process to
issue outbound HTTP requests against any host it can reach on the private
network. The path component is constrained to
`/uploads/attachments/-.` (built from a local-DB lookup),
whic
VulDB
apostrophecms apostrophe up to 4.30.0 server-side request forgery (GHSA-34pj-2622-jvxq)
vuldb·2026-06-13·CVSS 3.7
CVE-2026-53607 [LOW] apostrophecms apostrophe up to 4.30.0 server-side request forgery (GHSA-34pj-2622-jvxq)
A vulnerability, which was classified as critical, was found in apostrophecms apostrophe up to 4.30.0. The impacted element is an unknown function. The manipulation results in server-side request forgery.
This vulnerability is identified as CVE-2026-53607. The attack can be executed remotely. There is not any exploit available.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-06-12
Published