SEOmatic plugin for Craft CMS SSTI VulnerabilityGHSA-6j9m-rp7m-3gfg
HIGHFix: nystudio107/craft-seomatic@1e7d1d0GHSA-6j9m-rp7m-3gfg is a high-severity (CVSS 7.5) Code Injection vulnerability in nystudio107/craft-seomatic. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for nystudio107/craft-seomatic — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
nystudio107/craft-seomaticReal-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
A Server Side Template Injection (SSTI) was discovered in the SEOmatic plugin before 3.1.4 for Craft CMS, because requests that don't match any elements incorrectly generate the canonicalUrl, and can lead to execution of Twig code.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | nystudio107/craft-seomatic | all versions | 3.1.4composer require nystudio107/craft-seomatic:^3.1.4 |
Affected Products
seomaticnystudio107Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Craft CMS SEOmatic plugin 3.1.4 - Server-Side Template Injection
by 0xB455 · Jul 31, 2018
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nystudio107/craft-seomatic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nystudio107/craft-seomatic to 3.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6j9m-rp7m-3gfg is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-6j9m-rp7m-3gfg in your dependencies?
Find it across Packagist, including transitive dependencies.