tigroumeow AI Engine Plugin up to 3.6.5 on WordPress REST users endpoint reauth_for_authorize cross-site request forgery

Summaryinfo

A vulnerability has been found in tigroumeow AI Engine Plugin up to 3.6.5 and classified as problematic. Affected by this issue is the function reauth_for_authorize of the component REST users endpoint. The manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2026-15988. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in tigroumeow AI Engine Plugin up to 3.6.5. It has been rated as problematic. This issue affects the function reauth_for_authorize of the component REST users endpoint. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6.5 This is due to missing or incorrect nonce validation on the reauth_for_authorize function. This makes it possible for unauthenticated attackers to create new administrator accounts with attacker-supplied credentials via a CSRF-based REST authentication bypass, granted they can trick a site administrator into performing an action such as clicking on a link. This bypass can be combined with WordPress's ?_method=POST method-override support to convert a top-navigation GET request into an authenticated POST to the REST users endpoint, requiring no existing account on the attacker's part.

It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-15988 since 07/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful 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.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• tigroumeow

Name

• AI Engine Plugin

Version

• 3.6.0
• 3.6.1
• 3.6.2
• 3.6.3
• 3.6.4
• 3.6.5

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion