CVE-2020-29553: Grav CMS Cross-Site Request Forgery (CSRF)

getgrav/grav Updated 02 Oct 2025

Summary

24/05/2022
No i
High
8.8

CVE-2020-29553: Grav CMS Cross-Site Request Forgery (CSRF). Affects getgrav/grav across 2 version ranges.

< 1.6.30 >= 1.7.0-beta.1, <= 1.7.0-rc.17

No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Grav CMS is an open-source flat-file content management system that allows users to create and manage websites. It is built on PHP and provides a flexible and easy-to-use platform for content creation. However, Grav CMS versions up to 1.7.0-rc.17 are vulnerable to Cross-Site Request Forgery (CSRF) attacks.

Vulnerability Detail

The vulnerability in Grav CMS allows an attacker to execute a system command by tricking an admin into visiting a malicious website. This is possible due to a lack of proper CSRF protection in the Scheduler component. An attacker can craft a CSRF attack that, when triggered by the admin's visit to the malicious website, executes a system command on the target server. This can lead to unauthorized access, data leakage, or even complete compromise of the affected system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If upgrading to the latest version is not immediately possible, a temporary workaround is to disable the Scheduler component in Grav CMS. This can be done by removing or commenting out the relevant code in the configuration files. However, this workaround should only be considered as a temporary measure until the system can be upgraded to a secure version.

Conclusion

In conclusion, Grav CMS versions up to 1.7.0-rc.17 are vulnerable to a Cross-Site Request Forgery (CSRF) attack in the Scheduler component. This vulnerability allows an attacker to execute system commands on the target server by tricking an admin into visiting a malicious website. It is crucial to upgrade Grav CMS to version 1.7.0 or later to mitigate this vulnerability. If immediate upgrade is not possible, disabling the Scheduler component can serve as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for getgrav/grav →

Share this vulnerability

FAQ

Grav CMS is an open-source flat-file content management system that allows users to create and manage websites. It is built on PHP and provides a flexible and easy-to-use platform for content creation.

Cross-Site Request Forgery (CSRF) is a type of attack where an attacker tricks a user into performing an unwanted action on a website without their knowledge or consent. In the case of this vulnerability, an attacker can execute a system command on the target server by tricking an admin into visiting a malicious website.

The potential consequences of this vulnerability include unauthorized access to the affected system, data leakage, and complete compromise of the system. An attacker can execute arbitrary system commands, which can lead to various malicious activities depending on the attacker's intentions.

To protect your Grav CMS installation from this vulnerability, it is recommended to upgrade to version 1.7.0 or later. Additionally, it is important to follow security best practices, such as keeping the software up to date, using strong passwords, and regularly monitoring for any suspicious activity.

Yes, a temporary workaround is to disable the Scheduler component in Grav CMS. This can be done by removing or commenting out the relevant code in the configuration files. However, it is important to note that this workaround should only be considered as a temporary measure until the system can be upgraded to a secure version.

Related vulnerabilities

Recent vulnerabilities recorded for getgrav/grav.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback