SQL Injection Vulnerability in BEdita
Summary
CVE-2019-15570: BEdita vulnerable to SQL injection. Affects bedita/bedita versions < 4.0.0. Fixed in 4.0.0. 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
BEdita is an open-source content management system that allows users to create and manage digital content. It provides a flexible and extensible platform for building websites, web applications, and APIs. However, BEdita versions up to 4.0.0-RC2 are vulnerable to SQL injection attacks. This vulnerability occurs during a save operation for a relation with parameters, as the application fails to properly escape JSON data.
Vulnerability Detail
The SQL injection vulnerability in BEdita can be exploited by an attacker to manipulate database queries and potentially gain unauthorized access to sensitive information or modify data. By injecting malicious SQL code into the application, an attacker can bypass authentication mechanisms, extract data from the database, or even modify the database structure. This vulnerability has a critical severity rating with a CVSS score of 9.8.
How To Fix
Minimum fixed version
4.0.0
This is the first release that contains the fix.
composer require bedita/bedita:4.0.0Tip — 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 manually sanitize and escape JSON data before saving it to the database. This can be done by using appropriate escaping functions or libraries provided by the programming language or framework used in your application. It is important to thoroughly review and test the workaround to ensure it effectively mitigates the SQL injection vulnerability.
Conclusion
The SQL injection vulnerability in BEdita versions up to 4.0.0-RC2 can potentially lead to unauthorized access to sensitive data and data manipulation. It is crucial to upgrade to the latest version of BEdita (4.0.0 or later) to fix this vulnerability. If immediate upgrade is not possible, applying a temporary workaround to sanitize and escape JSON data can help mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for bedita/bedita →
FAQ
SQL injection is a type of security vulnerability where an attacker can insert malicious SQL code into an application's database query. This allows the attacker to manipulate the query and potentially gain unauthorized access to the database or modify its contents.
A successful SQL injection attack can lead to various consequences, including unauthorized access to sensitive information, data manipulation or deletion, bypassing authentication mechanisms, and even remote code execution.
You can use Vulert's playground at Vulert Scanner to check if your BEdita installation is affected by this vulnerability. Vulert analyzes your composer.lock file to identify any open-source vulnerabilities, including this SQL injection vulnerability.
At the time of this advisory, there are no known public exploits specifically targeting this SQL injection vulnerability in BEdita. However, it is crucial to promptly apply the recommended fix to mitigate the risk of potential attacks.
You can find more information about this vulnerability, including the technical details and the fix, in the GitHub advisory at the following URL: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-9gv2-2m38-j6cx/GHSA-9gv2-2m38-j6cx.json
