CVE-2020-18151: ThinkCMF Cross Site Request Forgerly (CSRF) vulnerability

thinkcmf/thinkcmf Updated 02 Oct 2025

Summary

24/05/2022
Yes i
Moderate
6.5

CVE-2020-18151: ThinkCMF Cross Site Request Forgerly (CSRF) vulnerability. Affects thinkcmf/thinkcmf versions < 6.0.8. Fixed in 6.0.8. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ThinkCMF is an open-source content management framework written in PHP. It provides a range of features for building websites and web applications. The framework is widely used and has a large user base. However, it is vulnerable to a Cross Site Request Forgery (CSRF) attack, which can allow an attacker to add an admin account.

Vulnerability Detail

The vulnerability in ThinkCMF arises from a lack of proper CSRF protection. This allows an attacker to trick a user into performing unintended actions on their behalf. In this case, an attacker can exploit the vulnerability to add an admin account, gaining unauthorized access to the system. This can lead to various malicious activities, such as data theft, privilege escalation, and unauthorized modification of content.

How To Fix

Minimum fixed version

6.0.8

This is the first release that contains the fix.

composer require thinkcmf/thinkcmf:6.0.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version is not immediately feasible, a temporary workaround is to implement CSRF protection manually. This can be done by adding CSRF tokens to all forms and verifying them on the server-side before processing any requests. The specific implementation details may vary depending on the application's architecture and framework.

Conclusion

In conclusion, the ThinkCMF framework is vulnerable to a Cross Site Request Forgery (CSRF) attack, which can allow an attacker to add an admin account. It is crucial to upgrade to the latest version or implement CSRF protection manually to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for thinkcmf/thinkcmf →

Share this vulnerability

FAQ

ThinkCMF is an open-source content management framework written in PHP. It provides a range of features for building websites and web applications.

A CSRF vulnerability allows an attacker to trick a user into performing unintended actions on their behalf. In this case, it can be exploited to add an admin account in ThinkCMF.

The consequences of this vulnerability include unauthorized access to the system, data theft, privilege escalation, and unauthorized modification of content.

To fix this vulnerability, it is recommended to upgrade ThinkCMF to version 6.0.8 or later. This version includes the necessary fixes and enhancements to mitigate the CSRF vulnerability.

If upgrading to the latest version is not immediately feasible, a temporary workaround is to implement CSRF protection manually by adding CSRF tokens to all forms and verifying them on the server-side.

Related vulnerabilities

Recent vulnerabilities recorded for thinkcmf/thinkcmf.

How To Fix

Minimum fixed version

6.0.8

This is the first release that contains the fix.

composer require thinkcmf/thinkcmf:6.0.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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