What is the CVSS score of CVE-2026-53607?

CVE-2026-53607 has a CVSS 3.1 base score of 3.7 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a patch available for CVE-2026-53607?

Yes, a patch is available for CVE-2026-53607. Update the affected software to the latest version immediately.

ApostropheCMS CVE-2026-53607

EUVD-2026-36576 LOW

Server-Side Request Forgery (SSRF) (CWE-918)

2026-06-12 GitHub_M

GHSA-34pj-2622-jvxq

Node.js SSRF Apostrophe

3.7

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

3.7 LOW

AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

vuln.today AI

4.0 MEDIUM

Non-default prettyUrls config justifies AC:H; SSRF probing of other systems justifies S:C; blind response oracle yields C:L with no integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 12, 2026 - 21:29 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Server-Side Request Forgery in ApostropheCMS through version 4.30.0 allows unauthenticated remote attackers to pivot the Node.js application process into issuing outbound HTTP requests to arbitrary hosts on the internal network when the prettyUrls SEO feature is explicitly enabled on the @apostrophecms/file module. The attack exploits the raw Host HTTP request header, which the pretty-URL handler uses verbatim to construct and fetch() an upstream URL, streaming the full HTTP response - status code, headers, and body - back to the requester. Practical impact is constrained to blind SSRF (network-topology probing via response-code and timing oracles, and verbose proxy or WAF error-body disclosure) rather than arbitrary data exfiltration; no patch exists at time of publication and no public exploit has been identified.

Technical ContextAI

The affected component is the public pretty-URL file handler in the @apostrophecms/file module of ApostropheCMS (CPE: cpe:2.3:a:apostrophecms:apostrophe:*). When prettyUrls: true is set in the module configuration, this handler accepts public HTTP requests for uploaded file attachments at clean, SEO-friendly URLs. It performs a local database lookup to construct a path constrained to /uploads/attachments/<cuid>-<slug>.<ext>, then builds the full upstream URL by prepending the raw value of the Host HTTP request header - a classic Host Header Injection leading to CWE-918 (Server-Side Request Forgery). The resulting URL is passed directly to Node.js fetch(), and the complete HTTP response is streamed back to the client with no sanitization. Because Host is fully attacker-controlled and no validation is applied, the server can be directed to connect to any TCP-accessible host on the application server's network. The cuid uniqueness in the path prevents cross-instance attachment exfiltration, but response-code differentials, timing side-channels, and any verbose error bodies returned by internal proxies, WAFs, or cloud metadata services remain accessible to the attacker.

RemediationAI

No vendor-released patch has been identified at time of analysis; GitHub Security Advisory GHSA-34pj-2622-jvxq (https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-34pj-2622-jvxq) should be monitored closely for a fix release. The most effective immediate compensating control is to disable the prettyUrls feature by setting prettyUrls: false or removing the option from the @apostrophecms/file module configuration - this eliminates the vulnerable handler entirely at the cost of losing SEO-friendly file URLs. If disabling prettyUrls is not operationally acceptable, a reverse proxy (e.g., nginx or a CDN edge layer) positioned in front of ApostropheCMS should be configured to enforce a static, canonical Host header value before requests reach the application, preventing attacker-supplied values from propagating to the SSRF-triggering code; this mitigation requires careful, ongoing proxy configuration maintenance to remain effective. Additionally, host-level or firewall egress filtering on the ApostropheCMS server should restrict outbound HTTP/HTTPS to only known-good upstream hosts, directly limiting the SSRF blast radius by blocking access to cloud metadata endpoints (169.254.169.254, fd00:ec2::254), internal Kubernetes APIs, and other unauthenticated internal services.