silverstripe-advancedworkflow vulnerable to remote code execution via advanced workflow email templateGHSA-39mm-rwm3-29jp
HIGHFix: silverstripe/silverstripe-advancedworkflow#629GHSA-39mm-rwm3-29jp is a high-severity (CVSS 7.2) CWE-1336 vulnerability in symbiote/silverstripe-advancedworkflow. A fix is available for symbiote/silverstripe-advancedworkflow — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-39mm-rwm3-29jp.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-39mm-rwm3-29jp by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
symbiote/silverstripe-advancedworkflow🐘symbiote/silverstripe-advancedworkflow🐘symbiote/silverstripe-advancedworkflowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Silverstripe Advanced Workflow is a highly configurable step-based workflow module. Prior to 6.4.5, 7.1.3, and 7.2.1, an attacker with permission to author the advanced workflow email template can place a specially crafted server-side template payload in NotifyUsersWorkflowAction.EmailTemplate. When NotifyUsersWorkflowAction renders the field through the Silverstripe template engine SSTemplateParser, the payload can cause PHP evaluation and arbitrary code execution on the server; the regression coverage is in tests/php/WorkflowEngineTest.php. This issue is fixed in versions 6.4.5, 7.1.3, and 7.2.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symbiote/silverstripe-advancedworkflow | all versions | 6.4.5composer require symbiote/silverstripe-advancedworkflow:^6.4.5 |
| 🐘Packagist | symbiote/silverstripe-advancedworkflow | ≥ 7.0.0&&< 7.1.3 | 7.1.3composer require symbiote/silverstripe-advancedworkflow:^7.1.3 |
| 🐘Packagist | symbiote/silverstripe-advancedworkflow | ≥ 7.2.0&&< 7.2.1 | 7.2.1composer require symbiote/silverstripe-advancedworkflow:^7.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symbiote/silverstripe-advancedworkflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symbiote/silverstripe-advancedworkflow to 6.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-39mm-rwm3-29jp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-39mm-rwm3-29jp in your dependencies?
Find it across Packagist, including transitive dependencies.