dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-13250

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Solace Extra WordPress plugin versions up to 1.5.3 lacks proper authorization checks on an AJAX action handler registered with wp_ajax_nopriv_, allowing unauthenticated users to delete all content imported via the Starter Template feature. The anti-CSRF nonce is exposed on every wp-admin page without page restrictions, and any subscriber-level user can retrieve it from /wp-admin/profile.php, making the deletion endpoint reachable and exploitable by fully unauthenticated attackers.

MitigationUpgrade to version 1.6.0 or later which adds proper capability checks and nonce verification to the AJAX handler. Until then, consider disabling the plugin or blocking the affected AJAX endpoints at the web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Solace Extra plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Solace Extra' in the list of installed plugins, or check the plugins directory for the solace-extra folder
    Affected if The plugin is present in the plugins directory
  2. Check installed plugin version
    In the Plugins list, find Solace Extra and note the version number displayed under the plugin name. Compare this version to the affected range (versions 1.5.3 and earlier)
    Affected if The installed version is 1.5.3 or earlier, or if no version number is displayed but the plugin is present
  3. Verify AJAX handler registration
    Examine the plugin PHP files and search for 'wp_ajax_nopriv_' hook registrations, specifically looking for any action handlers related to deleting or removing imported content
    Affected if The plugin registers AJAX handlers with wp_ajax_nopriv_ that handle deletion or removal of Starter Template content
  4. Confirm nonce exposure
    Visit any wp-admin page (such as /wp-admin/index.php) as a logged-in user and view the page source to locate the nonce value being exposed, or check /wp-admin/profile.php as a subscriber-level user
    Affected if Nonces are visible in the source of wp-admin pages without proper access restrictions
  5. Test unauthenticated endpoint accessibility
    Make a direct POST request to wp-admin/admin-ajax.php with action parameter matching the deletion handler (if identified) without providing authentication credentials
    Affected if The AJAX endpoint responds without requiring authentication or returns a successful deletion confirmation rather than an authorization error

The environment is affected if the Solace Extra plugin version is 1.5.3 or earlier and the plugin registers wp_ajax_nopriv_ handlers for content deletion functionality accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.6.0 or later which adds proper capability checks and nonce verification to the AJAX handler. Until then, consider disabling the plugin or blocking the affected AJAX endpoints at the web server level.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13250 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data