Cms version

Moderate effort

Found on 44% of audited stores.

Identify your ecommerce platform and CMS version, then ensure it is always kept up to date to protect your store from security vulnerabilities and avoid loss of vendor support.

What it is

Every online store runs on a content management system (CMS) or ecommerce platform — such as Shopify, WooCommerce, Magento, BigCommerce, or Wix. Each platform releases version updates that fix bugs, patch security holes, and add new features. When a security scanner cannot detect which platform or version your store is running, it usually means the information is hidden (which can be good), outdated, or the platform is self-hosted and unpatched. Keeping your CMS on a current, supported version is one of the most fundamental maintenance tasks for any online store.

Why it matters

Running an outdated or unknown CMS version is one of the leading causes of store hacks, data breaches, and payment fraud — all of which can result in lost customer trust, fines under regulations like GDPR and PCI-DSS, and even having your store blacklisted by Google (which directly destroys organic traffic overnight). Search engines also use site health signals — a hacked or flagged site loses rankings fast and is extremely difficult to recover. On the revenue side, a compromised checkout destroys conversions and can get your payment processor account terminated. Staying on a supported, up-to-date version means you receive security patches as soon as vulnerabilities are discovered, before attackers can exploit them.

How to fix it

  1. Identify which CMS or ecommerce platform your store is built on (check your hosting control panel, your developer, or your login URL — e.g. /wp-admin for WordPress, /admin for Shopify/Magento).
  2. Find the current version you are running — this is usually shown in your admin dashboard, under Settings, System Info, or About.
  3. Compare your installed version against the latest stable release published on the platform's official website or release notes.
  4. If you are on a hosted/SaaS platform (Shopify, BigCommerce, Wix, Squarespace, Webflow), confirm that automatic updates are enabled and that your theme and any installed apps or plugins are also up to date.
  5. If you are on a self-hosted platform (WooCommerce/WordPress, Magento/Adobe Commerce, PrestaShop, OpenCart), apply all available core, theme, and plugin/extension updates immediately — schedule a recurring monthly review.
  6. After updating, verify your store still functions correctly by testing the homepage, product pages, cart, and checkout flow, then re-run a security scan to confirm the issue is resolved.

Fix it on your platform

Pick your platform for the exact steps.

How to fix cms version on Shopify
  1. Shopify's core platform is SaaS and updated automatically — you do not manage core versions.
  2. Go to Shopify Admin → Online Store → Themes: check if your active theme has an 'Update available' banner and click 'Update theme' (save a backup first via 'Duplicate').
  3. Go to Shopify Admin → Apps: review all installed apps and ensure each is from an active, maintained developer — remove any apps that are no longer supported.
  4. Go to Shopify Admin → Settings → Plan to confirm your store is on an active plan with continued platform support.
How to fix cms version on Shopify Plus
  1. Core platform updates are managed by Shopify automatically.
  2. In your Shopify Plus admin, go to Online Store → Themes and apply any available theme updates after duplicating as a backup.
  3. Review all installed apps and custom channel integrations for version currency — contact your Shopify Plus Partner or Solutions Engineer for custom storefront (Hydrogen/Oxygen) version reviews.
  4. Check your Shopify Scripts and Checkout UI extensions for compatibility with the latest Shopify Checkout version.
How to fix cms version on WooCommerce
  1. Log in to WordPress Admin → Dashboard → Updates: you will see available updates for WordPress core, WooCommerce plugin, themes, and all other plugins.
  2. Click 'Update Now' for WordPress core first, then WooCommerce, then all remaining plugins and your active theme.
  3. Navigate to WooCommerce → Status → System Status to see a full report of your WooCommerce version, WordPress version, PHP version, and any environment issues flagged in red.
  4. Enable automatic background updates for minor releases: in WordPress Admin → Settings, or by adding `define('WP_AUTO_UPDATE_CORE', true);` to your wp-config.php.
  5. Schedule a monthly review and use a staging environment to test major updates before applying them to your live store.
How to fix cms version on WordPress.org
  1. Log in to WordPress Admin → Dashboard → Updates to see your current WordPress version and any available updates.
  2. Apply core, plugin, and theme updates from this single screen.
  3. Go to Dashboard → Updates → Automatic Updates to enable automatic minor core updates.
  4. Check that your PHP version (visible under Tools → Site Health → Info → Server) meets the minimum required by the latest WordPress release.
How to fix cms version on BigCommerce
  1. BigCommerce is a SaaS platform — core platform updates are applied automatically by BigCommerce.
  2. Log in to BigCommerce Admin → Storefront → Themes Marketplace: if your active theme has an update, you will see a notification — click 'Update & Preview' to review changes before publishing.
  3. Go to BigCommerce Admin → Apps → My Apps: review all installed apps for active maintenance status and remove deprecated ones.
  4. Check BigCommerce's release notes (via the BigCommerce Community or changelog) to understand what has changed and if any theme customizations need adjustments after platform updates.
How to fix cms version on Adobe Commerce (Magento)
  1. SSH into your server and run `php bin/magento --version` to confirm your current Adobe Commerce or Magento Open Source version.
  2. Check the Adobe Commerce release schedule and security advisories at the official Adobe Commerce developer documentation to identify the latest supported version.
  3. Use Composer to update: run `composer update magento/product-community-edition --with-all-dependencies` (or the Commerce equivalent) in your project root after backing up files and database.
  4. Run `php bin/magento setup:upgrade`, `php bin/magento setup:di:compile`, and `php bin/magento setup:static-content:deploy` after updating.
  5. Go to Admin → System → Web Setup Wizard (older versions) or use the Quality Patches Tool to apply individual security patches between major releases.
  6. Review and update all third-party extensions via Composer or the Adobe Commerce Marketplace after the core update.
How to fix cms version on Magento Open Source
  1. Run `php bin/magento --version` via SSH to check your current version.
  2. Review the Magento Open Source GitHub releases page for the latest version and security patches.
  3. Back up your database and files, then use Composer to pull in updates: `composer require magento/product-community-edition=<new-version> --no-update && composer update`.
  4. Run the post-upgrade commands: `php bin/magento setup:upgrade`, `php bin/magento setup:di:compile`, `php bin/magento cache:flush`.
  5. Test your store on a staging environment before deploying to production.
How to fix cms version on Wix
  1. Wix is a fully hosted SaaS platform — all core platform and infrastructure updates are applied automatically by Wix.
  2. Log in to your Wix account → Go to your site's Editor: check for any editor or template update notifications in the top bar or the Wix dashboard.
  3. Go to Wix Dashboard → Apps: review all installed Wix Apps to ensure they are up to date — Wix apps are generally updated automatically, but check for deprecation notices.
  4. If you use Wix Studio (formerly Editor X), review release notes in the Wix Studio dashboard for new feature rollouts that may require you to adjust site settings.
How to fix cms version on Squarespace
  1. Squarespace is a fully hosted SaaS platform — all core updates are applied automatically.
  2. Log in to Squarespace Admin → Pages or Design → Template: check if your template version has any available updates or migration notices from Squarespace (they email account owners).
  3. If you are on an older Squarespace 7.0 template, consider migrating to a Squarespace 7.1 template, which receives ongoing updates and new Commerce features.
  4. Go to Commerce → Extensions: review all connected extensions for active support status.
How to fix cms version on Webflow
  1. Webflow is a SaaS platform — core hosting and security updates are managed by Webflow automatically.
  2. Log in to Webflow Designer → check for any designer version update prompts or changelogs in the Webflow dashboard.
  3. Go to your Webflow Dashboard → Apps & Integrations: review all connected apps for supported status.
  4. If using Webflow Commerce, check the Webflow Commerce changelog for any feature changes that require configuration updates on your part.
How to fix cms version on PrestaShop
  1. Log in to PrestaShop Admin → Dashboard: look for the update notification widget that shows your current version vs. the latest available.
  2. Use the official '1-Click Upgrade' module (autoupgrade) — install it from PrestaShop Addons Marketplace if not already installed, then go to Modules → 1-Click Upgrade and run the upgrade wizard.
  3. Always back up your database and files before upgrading — the module prompts you to do this.
  4. After upgrading, go to Advanced Parameters → Information to confirm the new version is active and check for any module compatibility warnings.
How to fix cms version on OpenCart
  1. Log in to OpenCart Admin → Dashboard: the version number is shown in the bottom footer of the admin panel.
  2. Download the latest OpenCart release from the official OpenCart website and follow the official upgrade guide to apply it via FTP/SFTP.
  3. Back up your database and all files before any upgrade.
  4. After upgrading, go to Admin → Dashboard and verify the version number has changed, then test all storefront functions.
How to fix cms version on Drupal
  1. Log in to Drupal Admin → Reports → Available Updates to see your current Drupal core version and available updates for core and all modules.
  2. 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.
  3. Enable the Update Manager module (Admin → Extend) to receive in-dashboard update notifications.
  4. Review Drupal's Security Advisories page and subscribe to security email alerts for your installed version.
How to fix cms version on Joomla
  1. Log in to Joomla Admin → System → Update → Joomla to see your current version and available updates.
  2. Click 'Install the Update' to apply core updates directly from the admin panel.
  3. Go to System → Update → Extensions to update all installed extensions.
  4. 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 audit to find cms version — and every other issue — across your whole site in minutes.

Scan my site free

Frequently asked questions

What is Cms version?

Every online store runs on a content management system (CMS) or ecommerce platform — such as Shopify, WooCommerce, Magento, BigCommerce, or Wix. Each platform releases version updates that fix bugs, patch security holes, and add new features. When a security scanner cannot detect which platform or version your store is running, it usually means the information is hidden (which can be good), outdated, or the platform is self-hosted and unpatched. Keeping your CMS on a current, supported version is one of the most fundamental maintenance tasks for any online store.

Why does cms version matter?

Running an outdated or unknown CMS version is one of the leading causes of store hacks, data breaches, and payment fraud — all of which can result in lost customer trust, fines under regulations like GDPR and PCI-DSS, and even having your store blacklisted by Google (which directly destroys organic traffic overnight). Search engines also use site health signals — a hacked or flagged site loses rankings fast and is extremely difficult to recover. On the revenue side, a compromised checkout destroys conversions and can get your payment processor account terminated. Staying on a supported, up-to-date version means you receive security patches as soon as vulnerabilities are discovered, before attackers can exploit them.

How do I fix cms version?

Identify your ecommerce platform and CMS version, then ensure it is always kept up to date to protect your store from security vulnerabilities and avoid loss of vendor support.

Related Site Lifecycle issues