mediumCVE-2026-13250

Solace Extra <= 1.5.3 - Missing Authorization to Unauthenticated Arbitrary Content Deletion via delete_previously_imported AJAX Action

Q: What is affected by CVE-2026-13250?

Solace Extra versions listed as affected should be reviewed: *-1.5.3.

Q: 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.

Q: 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.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

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.

ProductSolace Extra

CVSS5.3

EPSS0.00273

UpdatedJuly 13, 2026

Quick answer

Solace Extra 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

*-1.5.3

Fixed versions

1.6.0

How to fix it

Solace Extra is affected by CVE-2026-13250, a authorization bypass issue in versions up to 1.5.3. Wordfence lists the official remediation as updating to version 1.6.0, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, WooCommerce checkout/account/vendor flows, Elementor/page-builder surfaces, reservation or booking workflows, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has Solace Extra installed, including production, staging, multisite, client, WooCommerce, marketplace, and booking environments.
Confirm the installed Solace Extra version and compare it with the affected range from the Wordfence advisory.
Update Solace Extra to version 1.6.0, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable Solace Extra or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review affected REST endpoints, AJAX actions, roles, capabilities, account changes, orders, bookings, payments, marketplace vendor actions, and admin actions for unauthorized activity.
Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running Solace Extra version is version 1.6.0 or newer, and record the patched version in the remediation ticket.
Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, account, vendor, payment, booking, invoice, or settings change.
Review web server, WordPress, security plugin, WAF, database, WooCommerce, and application logs for exploitation attempts before and after the fix.
Retest normal visitor, subscriber, customer, vendor, editor, administrator, checkout, form, API, booking, reservation, invoice, or integration workflows to confirm expected behavior still works.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress WooCommerce PHP Authorization Bypass

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-13250?

Solace Extra versions listed as affected should be reviewed: *-1.5.3.

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.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.