Cms version
Moderate effortFound on 37% of audited stores.
Update your CMS and ecommerce platform to the latest stable version immediately to close known security vulnerabilities and maintain vendor support.
What it is
Every website is built on a content management system (CMS) — software like WordPress, WooCommerce, Shopify, Wix, or Magento that powers your store behind the scenes. Just like your phone's operating system, this software releases regular updates that fix bugs, patch security holes, and add new features. Running an outdated version means your store is using software the vendor no longer actively protects — and that attackers actively target. A "cms_version" finding means your platform or a core component of it has been detected as out-of-date or approaching end-of-life.
Why it matters
Outdated CMS versions are the single most common entry point for store hacks: attackers maintain public databases of known vulnerabilities tied to specific version numbers, and they run automated bots that scan millions of sites daily looking for easy targets. A successful breach can result in stolen customer payment data (triggering PCI-DSS fines and card-network penalties), customer account takeovers, malware injected into your storefront that drives customers away, and Google Safe Browsing warnings that tank your organic traffic overnight. Beyond security, running end-of-life software means you stop receiving performance improvements and compatibility updates — slowing your site and hurting your search rankings. Many payment processors and hosting providers will also suspend service for stores running critically outdated platforms.
How to fix it
- Identify your current platform version: log into your admin dashboard and locate the version number (typically shown in the footer of the admin panel, a 'Dashboard > Updates' screen, or a 'System Info' page).
- Look up the current stable release on your platform's official website or changelog, and note any versions flagged as end-of-life (EOL) or no longer receiving security patches.
- Before updating, back up your entire store: database, theme files, uploaded media, and any plugin/extension files. Store the backup off-site (cloud storage or a local drive).
- Apply the update in a staging or test environment first if your host provides one. Verify that your theme, checkout flow, and key plugins still work correctly after the update.
- Apply the update to your live store during a low-traffic period (e.g., late night). Follow the platform's official upgrade guide step by step — do not skip intermediate major versions if upgrading across multiple major releases.
- After updating, clear all caches, test the full purchase flow end-to-end, and confirm the new version number is displayed in your admin dashboard. Schedule a recurring reminder (monthly) to check for future updates.
Fix it on your platform
Pick your platform for the exact steps.
How to fix cms version on WordPress.org
- Log in to wp-admin. The Dashboard > Home screen will show a banner if WordPress core is out of date.
- Go to Dashboard > Updates to see pending WordPress core, plugin, and theme updates all in one place.
- Click 'Update Now' under WordPress core. WordPress will download and apply the update automatically.
- On the same Updates screen, select all outdated plugins (including WooCommerce if installed) and click 'Update Plugins', then repeat for themes.
- If you are more than one major version behind (e.g., on 5.x and current is 6.x), read the official upgrade guide at wordpress.org/support/article/upgrading-wordpress before proceeding.
- Use the free 'Health Check & Troubleshooting' plugin or WP Staging to test updates safely before pushing to production.
How to fix cms version on WooCommerce
- WooCommerce is a WordPress plugin, so WordPress core must be updated first (see WordPress.org steps above).
- In wp-admin go to Dashboard > Updates. WooCommerce updates appear in the Plugins section.
- Before updating WooCommerce, note the current version, then click 'Update' next to WooCommerce.
- After updating WooCommerce, navigate to WooCommerce > Status > System Status and verify there are no red warnings about database updates; if prompted to run a database update, do so.
- Test add-to-cart, checkout, and payment flows thoroughly after each WooCommerce major version upgrade.
- Keep all WooCommerce extensions (payments, shipping, etc.) updated via Dashboard > Updates > Plugins to avoid compatibility gaps.
How to fix cms version on Shopify
- Shopify's core platform is SaaS (software-as-a-service) and is updated automatically by Shopify — you do not manage core version updates yourself.
- What you DO control: your theme version. In the Shopify admin go to Online Store > Themes. If your theme is a free Shopify theme, an 'Update available' badge appears; click 'Update theme' (Shopify creates a backup automatically).
- For paid/third-party themes, check the theme developer's changelog and download the latest version from your original purchase source, then upload it via Online Store > Themes > Add theme > Upload zip.
- Audit installed apps: go to Apps and remove any apps you no longer use, as abandoned apps can introduce vulnerabilities even on Shopify.
- Review Shopify's changelog at shopify.dev/changelog to understand what platform changes may affect your storefront and stay informed.
How to fix cms version on Shopify Plus
- Like standard Shopify, the core platform is maintained by Shopify and updated automatically.
- Theme updates: Online Store > Themes — follow the same theme-update process as Shopify (above).
- Shopify Plus merchants with custom Hydrogen/headless storefronts must manually update Hydrogen and Remix package versions in their codebase — check package.json and run 'npm outdated' or 'yarn outdated', then update and re-deploy.
- Work with your Shopify Plus Merchant Success Manager if you are on a legacy platform version or have custom checkout scripts that may break after platform changes.
How to fix cms version on BigCommerce
- BigCommerce core is SaaS and updated automatically — no manual core upgrades required.
- Theme updates: In BigCommerce admin go to Storefront > My Themes. If a newer version of your theme is available, a notification appears. Click 'Make a copy' first (to preserve your current settings), then apply the update.
- For Stencil CLI developers: run 'stencil pull' to fetch the latest framework updates, merge carefully, then run 'stencil push' to deploy.
- Check Apps > My Apps for any apps flagged as having updates, and update them individually.
- Monitor the BigCommerce status page and release notes (bigcommerce.com/release-notes) for upcoming changes that may affect custom integrations.
How to fix cms version on Wix
- Wix core is fully managed by Wix — no manual platform updates needed.
- If your site was built on an older Wix template or uses legacy Wix Apps, go to your Wix Dashboard > Apps > Manage Apps and check for any apps showing an 'Update' button.
- For Wix Velo (code) sites: review any npm packages added via the Packages & Apps panel in the Velo sidebar, and update outdated packages.
- If you are on the legacy Wix ADI or an old site structure and Wix is prompting a site migration, follow Wix's guided migration to move to the current editor to retain support.
How to fix cms version on Wix Studio
- Wix Studio (the successor to the Wix Editor for professional sites) is SaaS — core platform updates are handled automatically.
- Manage installed widgets and blocks: in the Studio editor open the Apps panel and check for updates to installed marketplace apps.
- For custom npm packages used in Velo/Studio code: open the IDE panel > Packages & Apps > npm, review installed packages, and update version numbers to the latest stable release.
How to fix cms version on Squarespace
- Squarespace is fully SaaS — core platform updates are automatic and you cannot control them.
- If you are on an older Squarespace template version (7.0 vs 7.1), Squarespace recommends migrating to 7.1 for ongoing feature and security support. Go to your Squarespace account dashboard to start a new 7.1 site if you are still on 7.0.
- Third-party code blocks and custom scripts injected via Settings > Advanced > Code Injection or individual page headers should be audited periodically — update any CDN-linked libraries to their latest versions.
How to fix cms version on Webflow
- Webflow's hosting platform is SaaS — core updates are managed by Webflow automatically.
- For Webflow sites using custom code (Page Settings > Custom Code or Site Settings > Custom Code), audit any JavaScript libraries loaded from CDNs and update version numbers in the script tags to the latest stable release.
- If using Webflow Apps (the Apps Marketplace), open the Apps panel in the Designer and check for update notices on installed apps.
- Webflow Commerce: payment integrations (Stripe) are managed by Webflow, but review your Webflow plan to ensure you are on a current commerce plan with full support.
How to fix cms version on Adobe Commerce (Magento)
- Log in to your server via SSH. Run 'php bin/magento --version' to confirm the exact installed version.
- Check the current stable release and security patches at experienceleague.adobe.com/docs/commerce-operations/release/versions.html.
- For security patches only (lower risk): download the patch from the Adobe Commerce release page and apply using 'composer require magento/product-community-edition <patch-version> --no-update && composer update'.
- For full version upgrades: follow the official Adobe Commerce Upgrade Guide (experienceleague.adobe.com). Key steps: update composer.json, run 'composer update', then 'php bin/magento setup:upgrade', 'setup:di:compile', 'setup:static-content:deploy', and 'cache:flush'.
- Always test on a staging environment first. Use the Adobe Upgrade Compatibility Tool ('vendor/bin/uct upgrade:check') to identify breaking changes in your custom code before upgrading production.
- After upgrading, reindex: 'php bin/magento indexer:reindex' and verify storefront, admin, and checkout functionality.
How to fix cms version on Magento Open Source
- Follow the same SSH/Composer-based upgrade process as Adobe Commerce (Magento) above.
- Check current releases at github.com/magento/magento2/releases.
- Run 'composer require magento/product-community-edition <new-version> --no-update && composer update' followed by the standard 'bin/magento setup:upgrade' sequence.
- Use the Upgrade Compatibility Tool and test on staging before touching production.
How to fix cms version on PrestaShop
- Log in to the PrestaShop back office. Go to Advanced Parameters > Information to see the installed version.
- Check the latest release at github.com/PrestaShop/PrestaShop/releases or prestashop-project.org.
- Use the official '1-Click Upgrade' module (available in the PrestaShop Addons marketplace) for minor/patch upgrades: Modules > Module Manager, search '1-Click Upgrade', install, then follow the wizard.
- For major version upgrades (e.g., 1.7 to 8.x), back up the database and files first, then follow the manual upgrade guide in PrestaShop documentation.
- After upgrading, clear the cache: Advanced Parameters > Performance > Clear Cache, and verify front-office and checkout.
How to fix cms version on OpenCart
- In the OpenCart admin go to Dashboard — the version number is displayed in the footer.
- Download the latest release from opencart.com/index.php?route=cms/download.
- Back up your database and all files via your hosting control panel (cPanel, Plesk) or FTP.
- Use the OpenCart upgrade package (not a fresh install) — copy the new files over the existing installation, then run the install/upgrade.php script via your browser and follow the prompts.
- After upgrading, delete the install/ directory, clear the cache under Admin > Dashboard > blue refresh buttons, and test the storefront.
How to fix cms version on Drupal
- Log in to Drupal Admin → Reports → Available Updates to see your current Drupal core version and available updates for core and all modules.
- Apply updates using Composer: `composer update drupal/core --with-all-dependencies`, then run `drush updatedb` or use the web-based update script at /update.php.
- Enable the Update Manager module (Admin → Extend) to receive in-dashboard update notifications.
- Review Drupal's Security Advisories page and subscribe to security email alerts for your installed version.
How to fix cms version on Joomla
- Log in to Joomla Admin → System → Update → Joomla to see your current version and available updates.
- Click 'Install the Update' to apply core updates directly from the admin panel.
- Go to System → Update → Extensions to update all installed extensions.
- Subscribe to the Joomla Security Announcements mailing list to be notified of new security releases.
Does your site have this issue?
Run a free SEOLZ scan to find cms version — and every other issue — across your whole site in minutes.
Scan my site freeFrequently asked questions
What is Cms version?
Every website is built on a content management system (CMS) — software like WordPress, WooCommerce, Shopify, Wix, or Magento that powers your store behind the scenes. Just like your phone's operating system, this software releases regular updates that fix bugs, patch security holes, and add new features. Running an outdated version means your store is using software the vendor no longer actively protects — and that attackers actively target. A "cms_version" finding means your platform or a core component of it has been detected as out-of-date or approaching end-of-life.
Why does cms version matter?
Outdated CMS versions are the single most common entry point for store hacks: attackers maintain public databases of known vulnerabilities tied to specific version numbers, and they run automated bots that scan millions of sites daily looking for easy targets. A successful breach can result in stolen customer payment data (triggering PCI-DSS fines and card-network penalties), customer account takeovers, malware injected into your storefront that drives customers away, and Google Safe Browsing warnings that tank your organic traffic overnight. Beyond security, running end-of-life software means you stop receiving performance improvements and compatibility updates — slowing your site and hurting your search rankings. Many payment processors and hosting providers will also suspend service for stores running critically outdated platforms.
How do I fix cms version?
Update your CMS and ecommerce platform to the latest stable version immediately to close known security vulnerabilities and maintain vendor support.