CVE-2026-4002 | petjeaf Petje.af Plugin up to 2.1.8 on WordPress ajax_revoke_token cross-site request forgery

VDB-357675 · CVE-2026-4002 · GCVE-0-2026-4002 PETJEAF PETJE.AF PLUGIN UP TO 2.1.8 ON WORDPRESS AJAX_REVOKE_TOKEN CROSS-SITE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.2 $0-$5k 2.09+ Summaryinfo A vulnerability has been found in petjeaf Petje.af Plugin up to 2.1.8 on WordPress and classified as problematic. Affected is the function ajax_revoke_token. Performing a manipulation results in cross-site request forgery. This vulnerability is known as CVE-2026-4002. Remote exploitation of the attack is possible. No exploit is available. Detailsinfo A vulnerability was found in petjeaf Petje.af Plugin up to 2.1.8 on WordPress. It has been classified as problematic. This affects the function ajax_revoke_token. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is: 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. The weakness was published by Youcef Hamdani. It is possible to read the advisory at wordfence.com. This vulnerability is uniquely identified as CVE-2026-4002 since 03/11/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Type WordPress Plugin Vendor petjeaf Name Petje.af Plugin Version 2.1.0 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 4.3 VulDB Meta Temp Score: 4.2 VulDB Base Score: 4.3 VulDB Temp Score: 4.2 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 4.3 CNA Vector (Wordfence): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Cross-site request forgery CWE: CWE-352 / CWE-862 / CWE-863 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 03/11/2026 CVE reserved 04/15/2026 +34 days Advisory disclosed 04/15/2026 +0 days VulDB entry created 04/15/2026 +0 days VulDB entry last update Sourcesinfo Advisory: wordfence.com Researcher: Youcef Hamdani Status: Not defined CVE: CVE-2026-4002 (🔒) GCVE (CVE): GCVE-0-2026-4002 GCVE (VulDB): GCVE-100-357675 Entryinfo Created: 04/15/2026 11:42 Changes: 04/15/2026 11:42 (65) Complete: 🔍 Cache ID: 99:662:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸