Hyvä shipped two updates in the week before Black Friday. On 10 November it published a security fix for the optional CMS Tailwind JIT module, and on 12 November it released Default Theme 1.5.4 together with Theme Module 1.5.4. The first one is a patch you should apply now if the module is installed. The second one is a regular release, but several of its fixes touch the cart, payment buttons and checkout, which are the parts of a store you least want to break in late November. Here is what changed and how to plan it.
1. CMS Tailwind JIT 2.0.5: a cross-site scripting fix
According to the Hyvä security changelog, the module's Tailwind compiler iframe accepted compile requests from any page through postMessage without checking who sent them. Because the compiler pages could be opened without logging in, a single click on a malicious page was enough to run an attacker's JavaScript on the store's origin. Under specific conditions the admin was affected too. Hyvä rates the issue Medium.
- Who is affected: stores that installed hyva-themes/magento2-cms-tailwind-jit, versions from 1.0.0 up to 2.0.5. It is not part of the Default Theme or the Theme Module, so stores without it are not affected. On Hyvä Commerce the module is always installed.
- The fix: update to 2.0.5 with composer update hyva-themes/magento2-cms-tailwind-jit. Hyvä says the 1.x versions do not get a fix.
- Don't skip the last step: redeploy static content and flush the cache afterwards. Otherwise browsers keep loading the old JavaScript bundles.
- Can't update today? Hyvä links an interim mitigation from its Hyvä Commerce security changelog entry.
A quick way to check: run composer show hyva-themes/magento2-cms-tailwind-jit in the project. If Composer says the package is not installed, this fix does not apply to you.
2. Default Theme and Theme Module 1.5.4: cart and payment fixes
Release 1.5.4 is mostly fixes. The ones most likely to matter during peak season, as listed in the Hyvä changelogs:
- Payment shortcut buttons in the cart drawer. Since 1.5.3, Apple Pay, Google Pay, PayPal and similar shortcut buttons could render but do nothing when clicked. 1.5.4 restores them. If you are on 1.5.3, test these buttons first.
- Guest shipping estimate on the cart page. Without the hyva-themes/magento2-graphql-tokens package, guest requests for the shipping estimate went to guest-carts/undefined. That is fixed, and the PayPal Express shortcut no longer sends quote_id=undefined.
- 500 error on some configurable products. Configurable products without available children could throw a 500 error on Magento 2.4.7 and 2.4.8.
- Sign-in redirect. A stale login redirect cookie could send customers to the wrong page after logging in. The sign-in link now uses a referer parameter.
- Breadcrumb structured data. With client-side breadcrumbs, product pages now only list Home and the product in BreadcrumbList data, instead of a referring category that may not contain the product.
- Tailwind CSS is updated from v4.3.1 to v4.3.5.
3. What's new for developers
- A new cart-drawer.shortcut-buttons container. Payment modules can add their own Alpine component there as a CSP-compatible replacement for the now deprecated extra_actions HTML in the cart section data.
- A privateContent Alpine store. Every customer section, for example $store.privateContent.cart, is available as a reactive, read-only store. Components can read it without an event listener, which also works with Alpine CSP. The private-content-loaded event is still supported.
- Default classes on Page Builder content. Page Builder primary and secondary buttons now get btn btn-primary and btn btn-secondary, and you can add classes per content type in di.xml.
If you maintain a payment module or any third-party script that injects buttons into the cart drawer, the deprecation of extra_actions is the item to put on your list.
How to plan it around Black Friday
- Patch the JIT module now if you have it. It is a small Composer update plus a static content deploy, and the risk sits on the storefront origin.
- Treat 1.5.4 as a normal theme release. Run it on staging first and test the cart drawer, payment shortcut buttons, guest shipping estimates and a full checkout, including a configurable product.
- If you can't fit a release in before your freeze, write down which of the fixes above affect you and schedule the upgrade for the first quiet week after the peak.
- Re-test everything that hooks into the storefront after a theme upgrade: tracking, reviews, payment buttons and any chat widget.
That last point includes AI assistants. Claspwell's sales assistant runs on Hyvä and Luma storefronts, and after any theme update it is worth a two-minute check that the chat window opens and that Add to cart on product cards still works. If something looks off after an upgrade, tell us and we will check it with you.
Sources: Hyvä security changelog, Hyvä Default Theme changelog, Hyvä Theme Module changelog.