CVE-2020-24912: Reflected XSS Vulnerability in qcubed
Summary
CVE-2020-24912: qcubed reflected cross-site scripting (XSS) vulnerability. Affects qcubed/qcubed versions < 3.2. Fixed in 3.2. How to fix ↓
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
qcubed is an open-source PHP framework that provides a rapid development environment for building web applications. It offers a range of features and components to simplify the development process and enhance productivity. The framework is widely used and has a large community of developers contributing to its growth and improvement. However, a vulnerability has been discovered in qcubed that allows for a reflected cross-site scripting (XSS) attack.
Vulnerability Detail
The vulnerability in qcubed (all versions including 3.1.1) resides in the 'profile.php' file, specifically in the 'stQuery' parameter. This parameter is not properly sanitized, allowing unauthenticated attackers to inject malicious scripts into the application. When a user with an active session visits a page that includes the vulnerable parameter, the injected script will be executed in the context of the user's session, potentially leading to session hijacking and unauthorized access to sensitive information. The impact of this vulnerability can be significant, as it can compromise the security and integrity of the affected application.
How To Fix
Minimum fixed version
3.2
This is the first release that contains the fix.
composer require qcubed/qcubed:3.2Tip — 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 can be implemented by manually sanitizing the 'stQuery' parameter in the 'profile.php' file. This can be done by using appropriate input filtering and validation functions to remove any potentially malicious scripts. Here is an example of how the 'stQuery' parameter can be sanitized:
$stQuery = filter_input(INPUT_GET, 'stQuery', FILTER_SANITIZE_STRING);
Conclusion
The reflected XSS vulnerability in qcubed poses a significant risk to the security and integrity of affected applications. It is crucial for users to upgrade to the latest version of qcubed (3.2 or later) to ensure that their applications are protected against this vulnerability. In the meantime, implementing the provided workaround can help mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for qcubed/qcubed →
FAQ
The vulnerability allows unauthenticated attackers to execute arbitrary scripts in the context of a user's session, potentially leading to session hijacking and unauthorized access to sensitive information.
All versions of qcubed up to and including 3.1.1 are affected by this vulnerability.
Yes, upgrading to version 3.2 or later of qcubed will fix this vulnerability.
A temporary workaround is to manually sanitize the 'stQuery' parameter in the 'profile.php' file.
You can find more information about this vulnerability in the official GitHub advisory: [link to advisory]
Related vulnerabilities
Recent vulnerabilities recorded for qcubed/qcubed.
