Taqnix <= 1.0.3 - Cross-Site Request Forgery to Account Deletion via 'taqnix_delete_my_account' AJAX Action
Strategic Overview
- Status
- Patched in 1.0.4
- Affected Plugin
- Taqnix
- Affected Version
<= 1.0.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-3565
At a glance
CVE-2026-3565 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Taqnix WordPress plugin, affecting versions <= 1.0.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.4; sites on affected versions should update now. Disclosed April 2026, reported by theviper17y.
Vulnerability Overview
The Taqnix plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.3. This is due to a missing nonce verification in the taqnix_delete_my_account() function, where the check_ajax_referer() call is explicitly commented out on line 883. This makes it possible for unauthenticated attackers to trick a logged-in non-administrator user into deleting their own account via a forged request granted they can trick the user into performing an action such as clicking a link or visiting a malicious page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Taqnix <= 1.0.3 carries this weakness at taqnix_delete_my_account(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Taqnix the fix is 1.0.4: builds <= 1.0.3 are affected, anything from 1.0.4 onward is not.
Remediation
Update to version 1.0.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Taqnix: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Taqnix 1.0.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C