Staging Environment: Content and features may be unstable or change without notice.

Advisory Weakness Curation

CVE-2020-11056

Progress 0 / 0

Advisory Summaries

github_osv/GHSA-px8v-hxxx-2rgh

Potential Code Injection in Sprout Forms ### Impact A potential Server-Side Template Injection vulnerability exists in Sprout Forms which could lead to the execution of Twig code. ### Patches The problem is fixed in`barrelstrength/sprout-forms:v3.9.0` which upgrades to `barrelstrength/sprout-base-email:v1.2.7` ### Workarounds Users unable to upgrade should update any Notification Emails to use the "Basic Notification (Sprout Email)" template and avoid using the "Basic Notification (Sprout Forms)" template or any custom templates that display Form Fields. ### References - See the release notes in the CHANGELOG https://github.com/barrelstrength/craft-sprout-forms/blob/v3/CHANGELOG.md#390---2020-04-09-critical - Credits to Paweł Hałdrzyński, Daniel Kalinowski from ISEC.PL https://isec.pl/ for discovery and responsible disclosure ### For more information If you have any questions or comments about this advisory: * Open an issue in the Sprout Forms repo https://github.com/barrelstrength/craft-sprout-forms/issues * Email us at [sprout@barrelstrengthdesign.com](mailto:sprout@barrelstrengthdesign.com)

gitlab/packagist/barrelstrength/sprout-base-email/CVE-2020-11056

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') In Sprout Forms before 3.9.0, there is a potential Server-Side Template Injection vulnerability when using custom fields in Notification Emails which could lead to the execution of Twig code. This has been fixed in 3.9.0.

gitlab/packagist/barrelstrength/sprout-forms/CVE-2020-11056

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') In Sprout Forms before 3.9.0, there is a potential Server-Side Template Injection vulnerability when using custom fields in Notification Emails which could lead to the execution of Twig code. This has been fixed in 3.9.0.