Contao up to 4.13.39/5.3.3 Frontend Form injection

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Contao up to 4.13.39/5.3.3. Impacted is an unknown function of the component Frontend Form Handler. Performing a manipulation results in injection. This vulnerability is cataloged as CVE-2024-28191. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Contao up to 4.13.39/5.3.3. This affects an unknown functionality of the component Frontend Form Handler. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on integrity. The summary by CVE is:

Contao is an open source content management system. Starting in version 4.0.0 and prior to version 4.13.40 and 5.3.4, it is possible to inject insert tags in frontend forms if the output is structured in a very specific way. Contao versions 4.13.40 and 5.3.4 have a patch for this issue. As a workaround, do not output user data from frontend forms next to each other, always separate them by at least one character.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-28191 since 03/06/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1055 for this issue.

Upgrading to version 4.13.40 or 5.3.4 eliminates this vulnerability. Applying the patch 388859dcf110ca70e0fae68a2a5579ab6a702919 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Contao

Version

• 4.13.0
• 4.13.1
• 4.13.2
• 4.13.3
• 4.13.4
• 4.13.5
• 4.13.6
• 4.13.7
• 4.13.8
• 4.13.9
• 4.13.10
• 4.13.11
• 4.13.12
• 4.13.13
• 4.13.14
• 4.13.15
• 4.13.16
• 4.13.17
• 4.13.18
• 4.13.19
• 4.13.20
• 4.13.21
• 4.13.22
• 4.13.23
• 4.13.24
• 4.13.25
• 4.13.26
• 4.13.27
• 4.13.28
• 4.13.29
• 4.13.30
• 4.13.31
• 4.13.32
• 4.13.33
• 4.13.34
• 4.13.35
• 4.13.36
• 4.13.37
• 4.13.38
• 4.13.39
• 5.3.0
• 5.3.1
• 5.3.2
• 5.3.3

License

• open-source

Website

• Product: https://github.com/contao/contao/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion