Skip to content

Contao Insert tag injection in forms

Moderate severity GitHub Reviewed Published Sep 24, 2020 in contao/contao • Updated Apr 22, 2024

Package

composer contao/contao (Composer)

Affected versions

>= 4.0.0, < 4.4.52
>= 4.5.0, < 4.9.6
>= 4.10.0, < 4.10.1

Patched versions

4.4.52
4.9.6
4.10.1
composer contao/core-bundle (Composer)
>= 4.0.0, < 4.4.52
>= 4.5.0, < 4.9.6
>= 4.10.0, < 4.10.1
4.4.52
4.9.6
4.10.1

Description

Impact

It is possible to inject insert tags in front end forms which will be replaced when the page is rendered.

Patches

Update to Contao 4.4.52, 4.9.6 or 4.10.1.

Workarounds

Disable the front end login form and do not use form fields with array keys such as fieldname[].

References

https://contao.org/en/security-advisories/insert-tag-injection-in-forms

For more information

If you have any questions or comments about this advisory, open an issue in contao/contao.

References

@leofeyer leofeyer published to contao/contao Sep 24, 2020
Reviewed Sep 24, 2020
Published to the GitHub Advisory Database Sep 24, 2020
Published by the National Vulnerability Database Oct 7, 2020
Last updated Apr 22, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(54th percentile)

Weaknesses

Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Learn more on MITRE.

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

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. Learn more on MITRE.

CVE ID

CVE-2020-25768

GHSA ID

GHSA-f7wm-x4gw-6m23

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.