CVE-2017-16558: Contao SQL injection in the backend and listing module

contao/contao Updated 02 Oct 2025

Summary

24/05/2022
No i
Critical
9.8

CVE-2017-16558: Contao SQL injection in the backend and listing module. Affects contao/contao across 2 version ranges.

>= 3.0.0, <= 3.5.30 >= 4.0.0, < 4.4.8

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

Contao is an open-source content management system (CMS) that allows users to create and manage websites. It provides various features and modules for website development, including a backend administration interface and a listing module for displaying content. However, versions 3.0.0 to 3.5.30 and 4.0.0 to 4.4.7 of Contao are vulnerable to an SQL injection attack in both the backend and listing module.

Vulnerability Detail

The SQL injection vulnerability in Contao allows an attacker to manipulate SQL queries and potentially gain unauthorized access to the database. This can lead to various security risks, such as unauthorized data disclosure, data modification, or even complete compromise of the system. The vulnerability arises from improper input validation and sanitization in the affected versions of Contao.

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 feasible, users can apply a temporary workaround by implementing proper input validation and sanitization in their custom code. This involves validating user input and using parameterized queries or prepared statements to prevent SQL injection attacks. Here is an example of how to use prepared statements in PHP:

$stmt = $pdo->prepare('SELECT * FROM users WHERE username = :username');
$stmt->bindParam(':username', $username);
$stmt->execute();
$result = $stmt->fetchAll();

Conclusion

Contao versions 3.0.0 to 3.5.30 and 4.0.0 to 4.4.7 are vulnerable to an SQL injection attack in the backend and listing module. Users should upgrade to version 4.4.8 or later to fix the vulnerability. If immediate upgrade is not possible, implementing proper input validation and sanitization in custom code can serve as a temporary workaround. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for contao/contao →

Share this vulnerability

FAQ

Contao is an open-source content management system (CMS) used for creating and managing websites. It provides various features and modules for website development.

Versions 3.0.0 to 3.5.30 and 4.0.0 to 4.4.7 of Contao are affected by this SQL injection vulnerability.

The SQL injection vulnerability in Contao can lead to unauthorized access to the database, data disclosure, data modification, or even complete compromise of the system.

To fix the vulnerability, it is recommended to upgrade Contao to version 4.4.8 or later. Alternatively, you can implement proper input validation and sanitization in your custom code.

Yes, if upgrading to the latest version is not immediately feasible, you can implement proper input validation and sanitization in your custom code to mitigate the risk of SQL injection attacks.

Related vulnerabilities

Recent vulnerabilities recorded for contao/contao.

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