CVE-2026-53607: CWE-918: Server-Side Request Forgery (SSRF) in apostrophecms apostrophe
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/<cuid>-<slug>.<ext>` (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.
AI Analysis
Technical Summary
CVE-2026-53607 is a Server-Side Request Forgery (SSRF) vulnerability in ApostropheCMS (Node.js CMS) versions up to and including 4.30.0. When the 'prettyUrls: true' option is enabled on the '@apostrophecms/file' module, the public pretty-URL handler constructs an upstream URL using the raw Host HTTP request header without validation. This URL is then fetched by the server, and the response is streamed back to the client. Because the Host header is attacker-controlled, an unauthenticated remote attacker can cause the server to make HTTP requests to arbitrary hosts accessible from the server's network. The path component is restricted to a pattern based on a local database lookup, limiting the ability to exfiltrate data across instances. However, blind SSRF remains possible, enabling network topology reconnaissance through response codes, timing differences, and verbose error messages from proxies or WAFs. As of the publication date, no patched versions or official fixes are available.
Potential Impact
An unauthenticated attacker can leverage this SSRF vulnerability to make the ApostropheCMS server issue HTTP requests to internal or otherwise inaccessible hosts within the server's network. While direct data exfiltration is mitigated by path constraints and unique identifiers, the attacker can perform network reconnaissance and fingerprint internal services via response timing and error message analysis. The confidentiality impact is low, with no integrity or availability impact reported.
Mitigation Recommendations
As of the current information, no official patch or fix is available for this vulnerability. Users should monitor the vendor's advisory channels for updates. Until a fix is released, consider disabling the 'prettyUrls' feature on '@apostrophecms/file' or restricting access to the vulnerable endpoint to trusted users or networks to reduce exposure. Avoid relying on the Host header for constructing upstream URLs or implement strict validation and sanitization of this header.
CVE-2026-53607: CWE-918: Server-Side Request Forgery (SSRF) in apostrophecms apostrophe
Description
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/<cuid>-<slug>.<ext>` (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.
CVSS v3.1
Score 3.7low
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53607 is a Server-Side Request Forgery (SSRF) vulnerability in ApostropheCMS (Node.js CMS) versions up to and including 4.30.0. When the 'prettyUrls: true' option is enabled on the '@apostrophecms/file' module, the public pretty-URL handler constructs an upstream URL using the raw Host HTTP request header without validation. This URL is then fetched by the server, and the response is streamed back to the client. Because the Host header is attacker-controlled, an unauthenticated remote attacker can cause the server to make HTTP requests to arbitrary hosts accessible from the server's network. The path component is restricted to a pattern based on a local database lookup, limiting the ability to exfiltrate data across instances. However, blind SSRF remains possible, enabling network topology reconnaissance through response codes, timing differences, and verbose error messages from proxies or WAFs. As of the publication date, no patched versions or official fixes are available.
Potential Impact
An unauthenticated attacker can leverage this SSRF vulnerability to make the ApostropheCMS server issue HTTP requests to internal or otherwise inaccessible hosts within the server's network. While direct data exfiltration is mitigated by path constraints and unique identifiers, the attacker can perform network reconnaissance and fingerprint internal services via response timing and error message analysis. The confidentiality impact is low, with no integrity or availability impact reported.
Mitigation Recommendations
As of the current information, no official patch or fix is available for this vulnerability. Users should monitor the vendor's advisory channels for updates. Until a fix is released, consider disabling the 'prettyUrls' feature on '@apostrophecms/file' or restricting access to the vulnerable endpoint to trusted users or networks to reduce exposure. Avoid relying on the Host header for constructing upstream URLs or implement strict validation and sanitization of this header.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T19:39:52.404Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c758ce617e2d834c30b83
Added to database: 06/12/2026, 21:09:32 UTC
Last enriched: 06/19/2026, 22:20:01 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 94
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.