QuickAppsCMS Cross-Site Request Forgery (CSRF) Vulnerability

quickapps/cms Updated 02 Oct 2025

Summary

14/05/2022
No i
High
8.8

CVE-2018-17102: QuickAppsCMS Cross-Site Request Forgery (CSRF). Affects quickapps/cms versions < 2.0.0-beta2. 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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

QuickAppsCMS (aka QACMS) is an open-source content management system designed to simplify the creation and management of websites. It provides a range of features and functionalities, including user management, content editing, and administration. However, QuickAppsCMS is vulnerable to a Cross-Site Request Forgery (CSRF) attack.

Vulnerability Detail

The CSRF vulnerability in QuickAppsCMS allows an attacker to change the administrator password by exploiting the user/me URI. This means that an unauthorized user can perform actions on behalf of the administrator without their knowledge or consent. The impact of this vulnerability is significant, as it grants the attacker full control over the website and its content. The vulnerability has a CVSS score of 8.8, indicating a high severity level.

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

There is no known workaround for this vulnerability. It is crucial to update to the latest version of QuickAppsCMS to mitigate the risk of CSRF attacks.

Conclusion

The CSRF vulnerability in QuickAppsCMS poses a significant risk to website security, as it allows an attacker to change the administrator password and gain full control over the website. To mitigate this vulnerability, it is crucial to update QuickAppsCMS to version 2.0.0-beta3 or later. For further support and assistance in vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for quickapps/cms →

Share this vulnerability

FAQ

A CSRF vulnerability allows an attacker to perform actions on behalf of an authenticated user without their consent or knowledge. It can lead to unauthorized changes, data theft, or other malicious activities.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your QuickAppsCMS installation is affected by this vulnerability. Simply upload your composer.lock file to the playground, and it will analyze and alert you if any open-source vulnerabilities are detected.

The CSRF vulnerability in QuickAppsCMS allows an attacker to change the administrator password, granting them full control over the website and its content. This can lead to unauthorized access, data manipulation, and potential damage to the website's reputation.

Yes, the developers of QuickAppsCMS have released a patch in version 2.0.0-beta3 and later. It is recommended to update to the latest version to fix the vulnerability and ensure the security of your website.

At the time of this advisory, there are no known public exploits specifically targeting this vulnerability in QuickAppsCMS. However, it is essential to address the vulnerability promptly by updating to the latest version to prevent any potential attacks.

Related vulnerabilities

Recent vulnerabilities recorded for quickapps/cms.

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