What is CVE-2020-11056?

CVE-2020-11056 is a critical-severity code injection vulnerability in barrelstrength/sprout-base-email (composer), affecting versions < 1.2.7. It is fixed in 1.2.7, 3.9.0. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2020-11056?

CVE-2020-11056 has a CVSS score of 7.4 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2020-11056?

barrelstrength/sprout-base-email (composer) versions < 1.2.7; barrelstrength/sprout-forms (composer) versions < 3.9.0.

Is there a fix for CVE-2020-11056?

Yes. CVE-2020-11056 is fixed in 1.2.7, 3.9.0. Upgrade to this version or later.

Is CVE-2020-11056 exploitable, and should I be worried?

Whether CVE-2020-11056 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-11056 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2020-11056?

Upgrade: barrelstrength/sprout-base-email to 1.2.7 or later, barrelstrength/sprout-forms to 3.9.0 or later.

CVE-2020-11056 in barrelstrength/sprout-base-email

Q: How severe is CVE-2020-11056?

CVE-2020-11056 has a CVSS score of 7.4 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2020-11056?

barrelstrength/sprout-base-email (composer) versions < 1.2.7; barrelstrength/sprout-forms (composer) versions < 3.9.0.

Q: Is there a fix for CVE-2020-11056?

Yes. CVE-2020-11056 is fixed in 1.2.7, 3.9.0. Upgrade to this version or later.

Q: Is CVE-2020-11056 exploitable, and should I be worried?

Whether CVE-2020-11056 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-11056 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-11056?

Upgrade: barrelstrength/sprout-base-email to 1.2.7 or later, barrelstrength/sprout-forms to 3.9.0 or later.

Summary

Potential Code Injection in Sprout Forms

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
Credits to Paweł Hałdrzyński, Daniel Kalinowski from 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
Email us at [email protected]

Impact

A potential Server-Side Template Injection vulnerability exists in Sprout Forms which could lead to the execution of Twig code.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2020-11056 has a CVSS score of 7.4 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.7, 3.9.0); upgrading removes the vulnerable code path.

Affected versions

barrelstrength/sprout-base-email (< 1.2.7) barrelstrength/sprout-forms (< 3.9.0)

Security releases

barrelstrength/sprout-base-email → 1.2.7 (composer) barrelstrength/sprout-forms → 3.9.0 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem is fixed inbarrelstrength/sprout-forms:v3.9.0 which upgrades to barrelstrength/sprout-base-email:v1.2.7

Frequently Asked Questions

What is CVE-2020-11056? CVE-2020-11056 is a critical-severity code injection vulnerability in barrelstrength/sprout-base-email (composer), affecting versions < 1.2.7. It is fixed in 1.2.7, 3.9.0. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2020-11056? CVE-2020-11056 has a CVSS score of 7.4 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2020-11056?
- barrelstrength/sprout-base-email (composer) (versions < 1.2.7)
- barrelstrength/sprout-forms (composer) (versions < 3.9.0)
Is there a fix for CVE-2020-11056? Yes. CVE-2020-11056 is fixed in 1.2.7, 3.9.0. Upgrade to this version or later.
Is CVE-2020-11056 exploitable, and should I be worried? Whether CVE-2020-11056 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-11056 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-11056?
- Upgrade barrelstrength/sprout-base-email to 1.2.7 or later
- Upgrade barrelstrength/sprout-forms to 3.9.0 or later