Quick answers
- Is CVE-2026-65693 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65693 being exploited in the wild.
- How severe is CVE-2026-65693?
- High severity, with a CVSS score of 7.2, published 24 July 2026.
- Which products and versions are affected?
- Microweber <= 2.0.20.
- Is there a fix for CVE-2026-65693?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-65693 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-65693?
- Check whether you run Microweber at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Microweber CMS through 2.0.20 is vulnerable to Server-Side Template Injection (SSTI) leading to Remote Code Execution (RCE). The vulnerability exists in the TwigView::render() method and other inline Twig environments which fail to implement Twig's SandboxExtension or a SecurityPolicy. An authenticated administrator can inject malicious Twig expressions, such as filter('system'), into mail template bodies. These templates are stored unsanitized in the database and executed whenever a system event (like a checkout or registration) triggers a mail dispatch. As the project is reportedly abandoned, no official patch is available; users are advised to manually implement a strict Twig security policy or restrict access to the template editor.
Affected products
- Microweber Microweber CMS <= 2.0.20
Timeline
- 2026-07-15: disclosed: Vulnerability discovered and reported to VulnCheck
- 2026-07-23: advisory: Public disclosure via GitHub Gist
- 2026-07-24: other: CVE published to NVD dataset