CVE-2020-8134: Server-side request forgery in Ghost CMS
Summary
CVE-2020-8134: Server-side request forgery in Ghost CMS. Affects ghost versions < 3.10.0. Fixed in 3.10.0. How to fix ↓
Also tracked for
- ghost · Bitnami
The same CVE-2020-8134 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Ghost CMS is an open-source content management system designed for creating professional blogs and websites. It provides a user-friendly interface and a range of features for managing and publishing content. However, versions prior to 3.10.0 are vulnerable to a server-side request forgery (SSRF) attack. This vulnerability allows an attacker to manipulate the server to perform unauthorized actions, such as scanning local or external networks or interacting with internal systems.
Vulnerability Detail
The server-side request forgery (SSRF) vulnerability in Ghost CMS allows an attacker to exploit the application's functionality to send crafted requests to other internal or external systems. By manipulating the server, an attacker can bypass security measures and potentially gain unauthorized access to sensitive information or perform actions on behalf of the server. This vulnerability poses a moderate risk and can have serious consequences if exploited.
How To Fix
Latest published version: 6.72.0 as of 22 Oct 2026
npm install ghost@6.72.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.10.0
This is the first release that contains the fix.
npm install ghost@3.10.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If updating to the latest version is not immediately possible, a temporary workaround is to implement network-level controls to restrict outgoing requests from the application server. This can be achieved by configuring firewall rules or network proxies to block requests to external or potentially malicious destinations. However, this workaround is not a permanent solution and updating to the latest version is strongly advised.
Conclusion
In conclusion, the server-side request forgery (SSRF) vulnerability in Ghost CMS can allow an attacker to manipulate the server and perform unauthorized actions. It is crucial to update Ghost CMS to version 3.10.0 or later to mitigate this vulnerability. If immediate updating is not possible, implementing network-level controls can serve as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for ghost →
FAQ
A server-side request forgery (SSRF) vulnerability is a type of security vulnerability that allows an attacker to manipulate a server to send crafted requests to other internal or external systems. This can lead to unauthorized access to sensitive information or actions performed on behalf of the server.
Exploiting this vulnerability can result in unauthorized access to sensitive information, compromise of internal systems, and potential data breaches. It can also be used as a stepping stone for further attacks against the application or the underlying infrastructure.
You can use Vulert's playground at Vulert Scanner to check if your Ghost CMS installation is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the package-lock.json file.
Yes, a fix is available for this vulnerability. It is recommended to update Ghost CMS to version 3.10.0 or later, which includes a patch that addresses the SSRF vulnerability.
If updating to the latest version is not immediately possible, you can implement network-level controls to restrict outgoing requests from the application server. This can be achieved by configuring firewall rules or network proxies to block requests to external or potentially malicious destinations. However, this is not a permanent solution and updating to the latest version is strongly advised.
References
Related vulnerabilities
Recent vulnerabilities recorded for ghost.
