mediumCVE-2026-1832

ThriveDesk <= 2.1.7 - Missing Authorization to Authenticated (Subscriber+) Cache Deletion

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

Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk versions listed as affected should be reviewed: *-2.1.7.

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 ThriveDesk – Live Chat, AI Chatbot, Helpdesk & Knowledge Base plugin for WordPress is vulnerable to unauthorized cache deletion due to a missing capability check on the 'thrivedesk_clear_cache' AJAX action in all versions up to, and including, 2.1.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to clear the plugin's cache.

ProductAgentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk

CVSS4.3

EPSS0.00204

UpdatedJuly 13, 2026

Quick answer

Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk 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

*-2.1.7

Fixed versions

2.2.0

How to fix it

Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk is affected by CVE-2026-1832, a authorization bypass issue in versions up to 2.1.7. Wordfence lists the official remediation as updating to version 2.2.0, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or vulnerable feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk installed, including staging, multisite, client, and WooCommerce environments.
Confirm the installed Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk version and compare it with the affected range from the Wordfence advisory.
Update Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk to version 2.2.0, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review affected REST endpoints, AJAX actions, roles, capabilities, orders, appointments, account records, and payment or status changes for unauthorized activity.
Rotate administrator sessions, API keys, webhook secrets, and integration tokens if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, 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 Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk version is version 2.2.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, payment, appointment, account, or settings change.
Review web server, WordPress, security plugin, WAF, and application logs for exploitation attempts before and after the fix.
Retest normal user, admin, checkout, form, API, or integration workflows to confirm the update did not break expected behavior.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress 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 Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-1832?

Agentic Help Desk Plugin for WordPress – Live Chat, AI Chatbot & Ticketing – ThriveDesk versions listed as affected should be reviewed: *-2.1.7.

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.