# CVE-2026-3565: Taqnix <= 1.0.3 - Cross-Site Request Forgery to Account Deletion via 'taqnix_delete_my_account' AJAX Action

> Attackers can trick logged-in users into deleting their accounts via CSRF due to missing nonce verification in the Taqnix WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-g4r7-2w2r-848v

## What is CVE-2026-3565?

CVE-2026-3565 is a medium-severity vulnerability in Taqnix, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-3565?


## How do I fix CVE-2026-3565?

No fix has been published for CVE-2026-3565 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3565 being exploited?

There is no known exploitation of CVE-2026-3565 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3565 and fix it if it is affected.

What it is: CVE-2026-3565 is a medium-severity vulnerability in Taqnix, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-3565 in the wild and no public exploit code.

Affected product: Taqnix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3565/ (Markdown: https://insights.sbomify.com/CVE-2026-3565/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3565
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3565
- OSV: https://osv.dev/vulnerability/CVE-2026-3565

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3565/
Summaries are generated and may contain mistakes; the official description above is the record.