CVE-2026-105682 in Ghost
Summary
by MITRE • 10/06/2026
Ghost is a Node.js content management system. From 1.18.0 until 6.27.0, an SSRF vulnerability in the webhooks feature allowed staff users to probe internal hosts from the Ghost server. This issue is fixed in version 6.27.0.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/06/2026
The discovery of a Server-Side Request Forgery (SSRF) vulnerability within the Ghost content management system highlights critical security gaps in how web applications handle outbound network requests, particularly when triggered by authenticated users. Ghost, a popular open-source publishing platform built on Node.js, processes various automated tasks through its webhook functionality, which allows external services to be notified of events such as new posts or user sign-ups. Between versions 1.18.0 and 6.27.0, the implementation of this feature failed to adequately validate or restrict the destination URLs provided by staff users when configuring webhooks. This oversight created a pathway for an attacker with staff-level privileges to manipulate the server into making HTTP requests to arbitrary internal addresses that are not accessible from the public internet.
The technical flaw stems from insufficient input validation and URL scheme filtering within the webhook configuration module. When a staff user defines a new webhook endpoint, the application accepts the provided URL without sufficiently checking whether it points to private IP ranges or localhost interfaces. By crafting specific payloads targeting internal services such as database servers, administrative panels, or cloud metadata endpoints like AWS EC2 instance metadata service, an attacker can force the Ghost server to act as a proxy. This capability allows the attacker to probe the internal network topology, identify running services on non-standard ports, and potentially exfiltrate sensitive data from unprotected internal APIs that trust requests originating from trusted application servers.
The operational impact of this vulnerability is significant for organizations relying on Ghost for their digital presence or internal documentation systems. While an SSRF attack typically requires some level of initial access, the fact that it can be exploited by staff users lowers the barrier to entry compared to unauthenticated attacks. Once inside the network perimeter via these forged requests, attackers may achieve further compromise by interacting with vulnerable internal services, such as Redis instances without authentication or Kubernetes API servers exposed internally. This effectively bypasses traditional perimeter defenses since the traffic appears legitimate and originates from a trusted application server, making detection through standard firewall rules difficult without deep packet inspection or strict egress filtering policies.
To mitigate this risk, organizations must ensure they are running Ghost version 6.27.0 or later, where the developers have implemented stricter validation mechanisms to prevent access to private IP ranges and loopback addresses. For environments that cannot immediately upgrade, network-level controls such as firewall rules restricting outbound traffic from application servers to only known external domains can provide a compensating control. Additionally, implementing strict egress filtering using cloud security groups or on-premise firewalls to block requests to internal CIDR blocks is essential. From a defense-in-depth perspective, this vulnerability aligns with CWE-918, which addresses Server-Side Request Forgery flaws, and maps to the MITRE ATT&CK technique T1571, indicating that defenders should monitor for unusual outbound connection patterns originating from web application servers to internal network segments.