HomeWordPress vulnerabilitiesSolace Extra
Solace Extra vulnerabilities
Solace Extra has 6 known vulnerabilities in this database. The most recent published record is dated 30 Sep 2026.
- Known vulnerabilities
- 6
- Active installs
- 10,000+
- Latest version
- 1.7.3
- Last updated
- 25 Sep 2026
- Most recent
- 30 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2026-80333 | Medium 5.3 | Before 1.7.2 | Fixed in 1.7.2 | 7 d ago |
| Sensitive data exposure CVE-2026-16966 | Medium 5.3 | Before 1.7.0 | Fixed in 1.7.0 | 2 Sep 2026 |
| Broken access control CVE-2026-18316 | Critical 9.1 | Up to 1.6.0 | Fixed in a later version (latest 1.7.3) | 16 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2026-16965 | Medium 4.3 | Before 1.6.1 | Fixed in 1.6.1 | 9 Aug 2026 |
| Broken access control CVE-2026-16948 | High 8.1 | Before 1.6.1 | Fixed in 1.6.1 | 8 Aug 2026 |
| Broken access control CVE-2026-13250 | Medium 5.3 | Up to 1.5.3 | Fixed in a later version (latest 1.7.3) | 11 Jul 2026 |
Read the published descriptions
- CVE-2026-80333, 30 Sep 2026
- The Solace Extra WordPress plugin before 1.7.2 does not perform any authorization or post-status checks on its front-end preview routes, allowing unauthenticated visitors to read the rendered content of non-published posts and pages of any type that WordPress would otherwise not serve. CVE record
- CVE-2026-16966, 2 Sep 2026
- The Solace Extra WordPress plugin before 1.7.0 does not perform any authorization or post-status checks in one of its AJAX actions, allowing unauthenticated visitors to read the content of non-published (draft, pending, private, and trashed) Site Builder parts that WordPress would otherwise not serve. CVE record
- CVE-2026-18316, 16 Aug 2026
- The Solace Extra plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on the import_zip() function in versions up to, and including, 1.6.0. The handler is registered on both wp_ajax_action-import-zip and wp_ajax_nopriv_action-import-zip and only verifies the 'ajax-nonce' nonce, which is emitted on every admin page via wp_localize_script (unrestricted admin_enqueue_scripts hook) and is therefore accessible to any authenticated user including Subscribers. This makes it possible for authenticated attackers, with Subscriber-level access and above, to wipe navigation menus, sidebar widgets (via update_option('sidebars_widgets', array())), all theme mods (via remove_theme_mods()), and Elementor templates, as well as trigger arbitrary demo-content imports. CVE record
- CVE-2026-16965, 9 Aug 2026
- The Solace Extra WordPress plugin before 1.6.1 does not perform capability or nonce checks in one of its AJAX actions, allowing any authenticated user such as a subscriber (and, via CSRF, any logged-in user) to update post meta on arbitrary posts and to deactivate the site's active templates. CVE record
- CVE-2026-16948, 8 Aug 2026
- The Solace Extra WordPress plugin before 1.6.1 does not perform capability checks in several of its AJAX actions and exposes the nonce that protects them on admin pages reachable by low-privileged users, allowing users with a role as low as Subscriber to modify site-wide presentation settings and delete imported site-builder content. CVE record
- CVE-2026-13250, 11 Jul 2026
- The Solace Extra plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.5.3. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to permanently delete all content previously imported via the Starter Template feature, including posts, pages, media attachments, WooCommerce products, taxonomy terms, and sitebuilder templates. The required nonce is emitted on every wp-admin page via wp_localize_script() hooked to admin_enqueue_scripts without a page guard, meaning any Subscriber visiting /wp-admin/profile.php can obtain it; the handler is additionally registered via wp_ajax_nopriv_, making it reachable by fully unauthenticated users as well. CVE record
What to do if you run Solace Extra
If you run Solace Extra, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Solace Extra vulnerabilities
Free. We email you when a new vulnerability is published for Solace Extra, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.