https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 16:50:35 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-59989 <p>Phalcon is a high-performance, full-stack PHP framework. In 5.15.0 and earlier, resolveFilter in phalcon/Mvc/View/Engine/Volt/Compiler.zep builds the join filter by inserting the raw separator and array token values into generated PHP without passing them through expression(). An attacker who can influence Volt template source can place quote-breaking content in a join argument, inject PHP into the compiled cache file, and execute it when Phalcon\Mvc\View\Engine\Volt::render() loads the template. This issue is fixed in version 5.16.0.</p> <p>Phalcon is a high-performance, full-stack PHP framework. In 5.15.0 and earlier, resolveFilter in phalcon/Mvc/View/Engine/Volt/Compiler.zep builds the join filter by inserting the raw separator and array token values into generated PHP without passing them through expression(). An attacker who can influence Volt template source can place quote-breaking content in a join argument, inject PHP into the compiled cache file, and execute it when Phalcon\Mvc\View\Engine\Volt::render() loads the template. This issue is fixed in version 5.16.0.</p> https://db.gcve.eu/vuln/fkie_cve-2026-59989 https://db.gcve.eu/vuln/ghsa-hrwp-4hh9-c8r8 <p><strong>Affected:</strong> Packagist: phalcon/cphalcon</p> <p>## Summary</p> <p>The Volt template compiler in Phalcon generates the PHP for the `join` filter by string-concatenating the filter&#39;s **raw template-literal argument bytes** with no escaping. The separator literal is dropped verbatim between two single quotes the compiler emits, and the piped array argument is emitted completely bare. A Volt template whose `join` arguments are attacker-influenced can therefore break out of the generated `join(&#39;…&#39;)` call and inject arbitrary PHP into the compiled template. Volt writes that compiled template to a cache file and `require()`s it at render time, so the injected PHP executes i.e. compile-time PHP code injection (server-side template injection -&gt; remote code execution) for any application that compiles attacker-controlled Volt source.</p> <p>## Details</p> <p>### Root cause</p> <p>`phalcon/Mvc/View/Engine/Volt/Compiler.zep:2544-2546`:</p> <p>```zephir case &#34;join&#34;: return &#34;join(&#39;&#34; . funcArguments[1][&#34;expr&#34;][&#34;value&#34;] . &#34;&#39;, &#34; . funcArguments[0][&#34;expr&#34;][&#34;value&#34;] . &#34;)&#34;; ```</p> <p>`funcArguments[1][&#34;expr&#34;][&#34;value&#34;]` (the separator) and `funcArguments[0][&#34;expr&#34;][&#34;value&#34;]` (the piped array) are the **raw values** of the parsed template tokens. Unlike every other expression in the compiler, they are **not** routed through `expression()` and receive no escaping: the separator value is spliced verbatim inside the `join(&#39;` … `&#39;` quotes with no neutralisation of `&#39;`, and the array value is emitted with no quoting at all. Volt&#39;s scanner stores string-literal bytes ver…</p> <p><strong>Affected:</strong> Packagist: phalcon/cphalcon</p> <p>## Summary</p> <p>The Volt template compiler in Phalcon generates the PHP for the `join` filter by string-concatenating the filter&#39;s **raw template-literal argument bytes** with no escaping. The separator literal is dropped verbatim between two single quotes the compiler emits, and the piped array argument is emitted completely bare. A Volt template whose `join` arguments are attacker-influenced can therefore break out of the generated `join(&#39;…&#39;)` call and inject arbitrary PHP into the compiled template. Volt writes that compiled template to a cache file and `require()`s it at render time, so the injected PHP executes i.e. compile-time PHP code injection (server-side template injection -&gt; remote code execution) for any application that compiles attacker-controlled Volt source.</p> <p>## Details</p> <p>### Root cause</p> <p>`phalcon/Mvc/View/Engine/Volt/Compiler.zep:2544-2546`:</p> <p>```zephir case &#34;join&#34;: return &#34;join(&#39;&#34; . funcArguments[1][&#34;expr&#34;][&#34;value&#34;] . &#34;&#39;, &#34; . funcArguments[0][&#34;expr&#34;][&#34;value&#34;] . &#34;)&#34;; ```</p> <p>`funcArguments[1][&#34;expr&#34;][&#34;value&#34;]` (the separator) and `funcArguments[0][&#34;expr&#34;][&#34;value&#34;]` (the piped array) are the **raw values** of the parsed template tokens. Unlike every other expression in the compiler, they are **not** routed through `expression()` and receive no escaping: the separator value is spliced verbatim inside the `join(&#39;` … `&#39;` quotes with no neutralisation of `&#39;`, and the array value is emitted with no quoting at all. Volt&#39;s scanner stores string-literal bytes ver…</p> https://db.gcve.eu/vuln/ghsa-hrwp-4hh9-c8r8