Which versions of craftcms/webhooks are affected by CVE-2026-32261?

craftcms/webhooks (composer) versions >= 3.0.0, < 3.2.0 is affected.

Is there a fix for CVE-2026-32261?

Yes. CVE-2026-32261 is fixed in 3.2.0. Upgrade to this version or later.

Is CVE-2026-32261 exploitable, and should I be worried?

Whether CVE-2026-32261 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-2026-32261 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.

CVE-2026-32261 in craftcms/webhooks

Q: What is CVE-2026-32261?

CVE-2026-32261 is a high-severity security vulnerability in craftcms/webhooks (composer), affecting versions >= 3.0.0, < 3.2.0. It is fixed in 3.2.0.

Q: Is there a fix for CVE-2026-32261?

Yes. CVE-2026-32261 is fixed in 3.2.0. Upgrade to this version or later.

Q: Is CVE-2026-32261 exploitable, and should I be worried?

Whether CVE-2026-32261 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-2026-32261 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-2026-32261?

Upgrade craftcms/webhooks to 3.2.0 or later.

CVE-2026-32261

CVE-2026-32261 is a high-severity security vulnerability in craftcms/webhooks (composer), affecting versions >= 3.0.0, < 3.2.0. It is fixed in 3.2.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

RCE via SSTI for users with permissions to access the Craft CMS Webhooks plugin

The Webhooks plugin renders user-supplied template content through Twig’s renderString() function without sandbox protection. This allows an authenticated user with access to the Craft control panel and permissions to access the Webhooks plugin to inject Twig template code that calls arbitrary PHP functions.

This is possible even if allowAdminChanges is set to false.

Affected users should update to version 3.2.0 to mitigate the issue.

Impact

Affected versions

craftcms/webhooks (>= 3.0.0, < 3.2.0)

Security releases

craftcms/webhooks → 3.2.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

Upgrade craftcms/webhooks to 3.2.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-32261? CVE-2026-32261 is a high-severity security vulnerability in craftcms/webhooks (composer), affecting versions >= 3.0.0, < 3.2.0. It is fixed in 3.2.0.
Which versions of craftcms/webhooks are affected by CVE-2026-32261? craftcms/webhooks (composer) versions >= 3.0.0, < 3.2.0 is affected.
Is there a fix for CVE-2026-32261? Yes. CVE-2026-32261 is fixed in 3.2.0. Upgrade to this version or later.
Is CVE-2026-32261 exploitable, and should I be worried? Whether CVE-2026-32261 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-2026-32261 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-2026-32261? Upgrade craftcms/webhooks to 3.2.0 or later.