weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot <= 2.3.0 - Missing Authorization to Authenticated (Subscriber+) Data Migration via wedocs_migrate_betterdocs_to_wedocs AJAX Action
The weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 2.3.0. This is due to a missing capability check on the do_migration() function registered as the wedocs_migrate_betterdocs_to_wedocs AJAX action, which performs no nonce verification via check_ajax_referer() and no capability check via current_user_can() before executing sensitive operations. This makes it possible for authenticated attackers, with Subscriber-level access and above, to trigger a full BetterDocs-to-weDocs data migration, creating and modifying 'docs' custom post type entries with attacker-controlled titles, updating site options, and deactivating the BetterDocs and BetterDocs Pro plugins via deactivate_plugins().
Quick answer
weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot 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.3.0
Fixed versions
- 2.3.1
How to fix it
weDocs is affected by CVE-2026-12729, missing authorization in the BetterDocs-to-weDocs migration AJAX action in *-2.3.0. Prioritize production WordPress sites where the plugin or theme is enabled, especially if subscriber or higher users can reach the vulnerable workflow. The recommended remediation is to update to version 2.3.1 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable feature, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses weDocs, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with the affected range: *-2.3.0.
- Apply the remediation: update to version 2.3.1 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable weDocs or restrict the affected admin, REST, AJAX, shortcode, upload, booking, ecommerce, profile, form, gallery, or theme workflow to trusted administrators only.
- Review application, web server, WordPress security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-12729.
- Remove suspicious stored content, uploaded files, generated logs, injected scripts, unexpected appointments/orders/posts, or altered configuration created through the affected workflow.
- Clear application, object, page, CDN, and browser caches after remediation so stale vulnerable responses or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm weDocs is no longer running *-2.3.0 and record the patched or mitigated version in the remediation ticket.
- Verify subscriber or higher users can no longer trigger the affected action or access data outside their intended permissions.
- Review logs before and after the fix for exploitation attempts, suspicious role activity, unexpected content changes, file reads, SQL errors, or unauthorized data access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-12729?
weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot versions listed as affected should be reviewed: *-2.3.0.
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.