# CVE-2026-4002: Petje.af <= 2.1.8 - Cross-Site Request Forgery to Account Deletion via 'petjeaf_disconnect' AJAX Action

> Unauthenticated attackers can force authenticated users to delete their Petje.af member accounts via CSRF due to missing nonce validation.

- **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:** 15 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-hx42-ggr3-3hp6

## What is CVE-2026-4002?

CVE-2026-4002 is a medium-severity vulnerability in petjeaf Petje.af, published on 15 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 Petje.af plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 2.1.8. This is due to missing nonce validation in the ajax_revoke_token() function which handles the 'petjeaf_disconnect' AJAX action. The function performs destructive operations including revoking OAuth2 tokens, deleting user meta, and deleting WordPress user accounts (for users with the 'petjeaf_member' role) without verifying the request originated from a legitimate source. This makes it possible for unauthenticated attackers to force authenticated users to delete their Petje.af member user accounts via a forged request granted the victim clicks on a link or visits a malicious site.

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

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


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

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

## Is CVE-2026-4002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4002 is a medium-severity vulnerability in petjeaf Petje.af, published on 15 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-4002 in the wild and no public exploit code.

Affected product: petjeaf Petje.af. 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-4002/ (Markdown: https://insights.sbomify.com/CVE-2026-4002/index.md)
```

## Sources

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

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