Mirasvit Full Page Cache Warmer Deserialization of Untrusted Data Vulnerability
Mirasvit Full Page Cache Warmer contains a deserialization of untrusted data vulnerability that could allow unauthenticated attackers to achieve remote code execution by supplying a crafted serialized PHP object in the CacheWarmer cookie.
Quick answer
Mirasvit Full Page Cache Warmer should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Update the Mirasvit Full Page Cache Warmer module to the fixed vendor release and review Magento for unauthorized access. Because Magento extensions run inside the storefront application, patching should include cache rebuilds, admin review, and credential rotation if exposure is suspected.
- Inventory every Magento or Adobe Commerce store using the Mirasvit Full Page Cache Warmer module.
- Upgrade the module to the fixed version from the Mirasvit security or changelog guidance using Composer or the vendor package.
- Run Magento setup upgrade, dependency injection compile, static content deployment, and cache flush as required by the deployment process.
- Restrict Magento admin access to trusted networks and MFA-protected administrator accounts.
- Review admin users, integrations, API tokens, cron entries, web roots, media directories, and generated code for unauthorized changes.
- Clear full-page cache, CDN cache, and opcache after deploying the fixed module.
- Rotate Magento admin, integration, deployment, database, and payment-related credentials if suspicious activity is found.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Composer and Magento module status show the fixed Mirasvit module version.
- Validate storefront cache warming, checkout, login, and admin workflows after deployment.
- Review Magento, web server, and WAF logs for exploit attempts or unexpected admin/API activity.
- Check file integrity for app/code, vendor, pub/media, generated, and cron-related paths.
- Run a Fixnx scan against the public storefront and confirm no vulnerable module signal remains.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-45247?
Mirasvit Full Page Cache Warmer should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
Why can this risk appear in multiple categories?
A vulnerability can belong to more than one platform or ecosystem. Fixnx keeps one canonical risk page while also listing it in every relevant category.