Ghost through 5.85.1 allows remote attackers to bypass an authentication rate-limit protection mechanism by using many X-Forwarded-For headers with different values. NOTE: the vendor's position is that Ghost should be installed with a reverse proxy that allows only trusted X-Forwarded-For headers.
The protection mechanism against excessive login attempts is based on identifying the client's IP address. An attacker can manipulate the X-Forwarded-For header by providing different, crafted IP address values in successive HTTP requests. The system reads these headers as different traffic sources and treats each request as coming from a different client, effectively bypassing the attempt counter and lockout mechanism. As a result, an attacker can attempt to guess passwords without limit and without risk of being blocked.
An attacker can conduct an effective brute-force attack on Ghost CMS user accounts, leading to unauthorized access to the administrative panel and potential takeover of full control over the platform and its content.
Ghost CMS should be updated to a version higher than 5.85.1 according to information in the vendor's references. The vendor additionally indicates that Ghost should be installed behind a reverse proxy configured to accept only trusted X-Forwarded-For headers — this is the recommended architectural mitigation regardless of software version.
Ghost CMS in versions up to and including 5.85.1, installations without a properly configured reverse proxy filtering X-Forwarded-For headers.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NGhost
APPGhost≤ 5.85.1
Related vulnerabilities
Ghost CMS: nieuwierzytelniony odczyt bazy danych przez SQL injection
Ghost CMS: stored XSS w pliku SVG umożliwia privilege escalation
Ghost CMS: Arbitrary File Upload umożliwiający wykonanie kodu (RCE)
Ghost v4.39.0 — przesyłanie plików SVG z potencjalnym wykonaniem kodu po stronie klienta
Ghost is a Node.js content management system. From version 5.101.6 to 6.19.2, incomplete CSRF protections arou...