Skip to content

Security Changelog - Hyvä Themes

This page documents security-relevant vulnerability fixes for Hyvä Themes (Default Theme and Theme Module).

CMS Tailwind JIT 2.0.5 - 2026-11-10

Cross-Site Scripting via the Tailwind JIT Compiler iframe

This issue applies to Hyvä Themes stores that have the optional CMS Tailwind JIT module (hyva-themes/magento2-cms-tailwind-jit) installed. The module is not part of the Default Theme or the Theme Module, so stores that haven't installed it are not affected. On Hyvä Commerce the module is always installed.

The module's Tailwind compiler iframe accepted compile requests from any page through postMessage, without checking which window or origin sent them. The Tailwind v3 compiler passed the received configuration to eval, and the Tailwind v4 compiler wrote the received content into the iframe document with innerHTML. Because the compiler pages can be opened without logging in, a single click on a malicious page was enough to run the attacker's JavaScript on the store origin. In the admin, the Tailwind v4 compiler iframe also wrote saved product, category and CMS content into a document on the admin origin.

  • Impact: Cross-Site Scripting (Storefront; Admin under specific conditions)
  • Severity: Medium
  • Affected versions: >= 1.0.0 < 2.0.5
  • Note: Update to 2.0.5 with composer update hyva-themes/magento2-cms-tailwind-jit. The 1.x versions do not receive a fix. After updating, redeploy the static content and flush the cache, otherwise browsers keep loading the old JavaScript bundles.

The full description, the behavior changes in 2.0.5 and an interim mitigation for stores that can't update right away are in the Hyvä Commerce security changelog entry.

Many thanks to Ilvars Švanda (Magebit), Emils Malovka (Magebit) and Maksim Soldatjonok for reporting this issue!

Full changelog entry for 2.0.5.

Default Theme 1.5.3, 1.4.11, 1.3.23 - 2026-10-12

Cross-Site Scripting in the MSRP Price and Popup Templates

Both MSRP templates escaped values for HTML while rendering them into JavaScript. In the price template this allowed a crafted product name to break out of the string and run script on the storefront for shoppers viewing the product, because the browser decodes the HTML entities in the x-data attribute before Alpine evaluates it. In the popup template a crafted MSRP explanation message could inject markup and script into the popup.

Both templates now escape these values for JavaScript. In 1.4.11 and 1.5.3 the MSRP templates are also made CSP safe, so child themes overriding Magento_Msrp/templates/popup.phtml or Magento_Msrp/templates/product/price/msrp.phtml need to update both templates together.

  • Impact: Cross-Site Scripting (Storefront)
  • Severity: Low
  • Affected versions: >= 1.3.6 < 1.3.23, >= 1.4.0 < 1.4.11, >= 1.5.0 < 1.5.3
  • Note: Exploiting this requires write access to product data, for example through the admin, a product import or the API, or admin access to the MSRP configuration. Because of the limited risk the fix ships with the regular releases and not as a separate patch release.

The Default Theme CSP is affected through the popup template only. Its MSRP price template already passes the product name to Alpine through a JSON encoded data attribute. Update to the same versions to get the fix.

Many thanks to Jelle Janssens (Singto BV) for reporting this issue!

Full changelog entry for 1.5.3, 1.4.11 and 1.3.23.