Avada 7.17 was released on 17 November 2026, and it is the latest version of Avada Classic. It includes a security fix, replaces the old iLightbox with Avada's own lighter lightbox, adds a spreadsheet-style editor to the Table element and reworks the Toggles and FAQ elements. You should update, because of the security fix, but test on a staging copy first and update the Avada Core and Avada Builder plugins at the same time as the theme.
This article is for business owners and agencies running Avada Classic sites: what changed, what can break and how to update safely.
What Avada 7.17 is and who it affects
Avada 7.17 is an update to Avada Classic. The Avada changelog page (opens in a new tab) lists 7.17 as the latest version, released on 17 November 2026, and the full changelog file (opens in a new tab) shows the previous release was 7.16.4 on 26 October 2026.
If you are not sure whether your site runs Classic or the new subscription product, Avada One, our article on Avada One vs Avada Classic explains the difference. This update is for Classic sites.
| Area | What changed in 7.17 | Who notices |
|---|---|---|
| Security | Fix in the Code Block element, plus ongoing hardening | Everyone, quietly |
| Lightbox | Native lightbox replaces iLightbox, new Global Options | Visitors opening images and galleries |
| Table element | Spreadsheet-style editor, merged cells, stack mode | Editors and phone visitors |
| Toggles and FAQ | New behaviour, styling and keyboard options | Visitors reading FAQs, editors |
| Plugin updates | Updating from Avada, then Plugins no longer deactivates the plugin | Whoever runs updates |
The security fix
The security fix is the main reason to update. The changelog describes it in one line: "Fixed possible Contributor+ level stored XSS vulnerability in the Code Block element". A second line mentions "ongoing security hardening across several areas of the product".
In plain words, stored XSS (cross-site scripting) means harmful script could be saved into a page and then run in the browser of anyone who views it. "Contributor+" means the person would need a WordPress account with at least Contributor access. Avada does not publish more detail than that, and we will not guess at it.
That is still a clear reason to update. If your site has several editor accounts, this is one more reason to remove the ones nobody uses.
The new lightbox
Avada 7.17 replaces iLightbox, the script Avada used for years to open images, galleries and videos in a popup, with its own lightbox. The changelog says the new one "needs no jQuery and only loads when a lightbox link is used". On its What's New page (opens in a new tab), Avada compares the two: about 28 KB of JavaScript for iLightbox against a new lightbox that starts with a 2.5 KB script.
For visitors, less code means a little less work for the browser, which helps on slower phones. It will not fix a slow site on its own. Avada says it only loads when a lightbox link is used.
For editors, there are new Global Options for the lightbox. Avada lists the colour scheme, transitions and slide direction, zoom, toolbar, arrows, thumbnails, title and caption layouts, and the screen sizes it opens on.
Table element: a spreadsheet-style editor
The Table element now has a spreadsheet-style editor. The changelog lists pasting from Excel or Google Sheets, merged cells, a responsive stack mode and a new Custom style with design options.
This saves editing time on price lists, opening hours and specification tables. The stack mode matters for visitors: Avada says it turns each row into a readable block on small screens, so phone visitors do not have to scroll sideways through a wide table.
Check your most important tables on a phone after updating.
Toggles and FAQ elements
The Toggles and FAQ elements have been reworked, and these sit on many business sites: service details, pricing questions and support pages. New options listed in the changelog include:
- Keep One Item Open, so one answer is always visible.
- Update URL, which gives every item its own shareable link, useful when your team wants to send a customer straight to one answer.
- Open and close speed, plus padding, borders, shadows, hover and active colours, item spacing and a rotating icon style.
Accessibility improved too. The changelog lists Space to open and close items, a visible focus ring for keyboard users, and support for reduced motion, so animations respect visitors who have asked their device for less movement.
The changelog also lists a long run of fixes for Toggles and FAQ. Because the element changed this much, FAQ pages with custom CSS are among the first pages we would check after the update.
What can break
7.17 touches elements found on many business sites, so a few areas deserve attention:
- Custom CSS and child themes written for the old lightbox, toggles or tables may target code that has changed.
- Third-party plugins that relied on iLightbox or on Avada's old toggle markup may behave differently.
- Out-of-step plugins. Avada's update guide (opens in a new tab) says the required plugins must be updated with every Avada update. A theme on 7.17 with older Avada Core or Avada Builder plugins can leave layouts broken or missing.
- Caches from your host, a caching plugin or a CDN can keep serving old scripts and styles, which looks like a broken page when it is not.
There is one helpful change here: the changelog says plugin updates on the Avada, then Plugins page no longer deactivate the plugin, so add-ons that depend on it stay active during the update. If an update does go wrong, our article on what to do when a WordPress update breaks your site explains how to recover.
How to update Avada 7.17 safely
A safe update protects the live site and checks the pages that changed. Avada's own guide says to take a full site and database backup before any update, and to update the required plugins with the theme.
- Full backup
- Staging copy
- Update theme, Avada Core and Avada Builder
- Clear caches
- Check key pages
- Update live site
- Back up the site and database, and make sure the backup can be restored.
- Update a staging copy first, with the Avada theme and the Avada Core and Avada Builder plugins together, then any other bundled plugins.
- Clear every cache: Avada's own caches, your caching plugin, the host cache and any CDN.
- Check the changed areas: pages with galleries or image popups, tables (on a phone too), toggles and FAQ pages, and any page using the Code Block element.
- Check forms and, for stores, checkout.
- Update the live site at a quiet time, clear caches again and repeat a quick check.
Sites that have skipped several versions should not jump straight to the newest one without care. Avada's guide says long-unupdated sites need to update in a sequential process to avoid issues.
Do it yourself or hire help?
A simple Avada site with no custom code and a working backup can usually be updated by its owner. Get help when the site brings in leads or sales, has custom code, runs WooCommerce, or has not been updated for months.
We test on staging and check the changed pages one by one. That is part of our Avada website development work, and ongoing updates are covered by website maintenance and support. If you want the speed benefit of the new lightbox to count, website performance optimisation looks at the rest of the page weight. Still deciding whether Avada is the right builder for you at all? Our Elementor vs Gutenberg vs Avada comparison sets out the trade-offs.
Where to start
Note your Avada, Avada Core and Avada Builder versions. If you are on 7.16.x, back up, update all three together on staging, clear caches and check your gallery, table and FAQ pages, then update the live site. If you are several versions behind, plan the update in steps.
Frequently asked questions
Is Avada 7.17 a security update?
Yes. Avada's changelog lists a fix for a possible stored XSS vulnerability in the Code Block element that needed Contributor access or higher, plus ongoing security hardening. Avada has not published further details, but the fix alone is a good reason to update.
Do I need to update Avada Core and Avada Builder too?
Yes. Avada says the required plugins must be updated with every Avada update. Running the 7.17 theme with older plugins can break layouts, so update all three together.
Will my old lightbox galleries still work after the update?
They should open in the new native lightbox, which replaces iLightbox. Avada's notes do not confirm that every old setting carries over, so check galleries on staging first.
Does Avada 7.17 apply to Avada One sites?
No. Avada 7.17 is a release of Avada Classic. Avada One is a separate product, explained in our article on Avada One vs Avada Classic. Avada One sites got their own big update, covered in Avada One 1.1: what to check before you update.
Sources
The facts in this article were checked against these pages, last reviewed 17 November 2026.
- Avada Changelog, Avada Classic Documentationclassic.avada.com/documentation/avada-changelog/
- Avada full changelog file, Avada Classicclassic.avada.com/wp-content/uploads/2023/03/changelog.txt
- What's New in Avada, Avada Classicclassic.avada.com/whats-new/
- How To Update The Avada Website Builder, Avada Classic Documentationclassic.avada.com/documentation/how-to-update-the-avada-website-builder/




