Skip to content

Product

wordpress ai-engine vulnerabilities

46 published CVES affecting wordpress ai-engine, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
46
Critical
3
High
21
Medium
22
Low
0
Unscored
0
CISA KEV
0

Latest wordpress ai-engine CVEs

Newest publication first · page 2 of 2

  1. HighCVSS 8.0 EPSS 0.37%

    The AI Engine plugin for WordPress is vulnerable to open redirect in version 2.8.4. This is due to an insecure OAuth implementation, as the 'redirect_uri' parameter is missing validation during the authorization flow. This makes it possible for unauthenticated attackers to interc...

  2. HighCVSS 7.2 EPSS 0.61%

    The AI Engine WordPress plugin before 2.6.5 does not sanitize and escape a parameter from one of its RESP API endpoint before using it in a SQL statement, allowing admins to perform SQL injection attacks

  3. MediumCVSS 4.7 EPSS 0.45%

    The AI Engine WordPress plugin before 2.4.8 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by admin users when viewing chatbot discussions.

  4. HighCVSS 7.2 EPSS 0.82%

    AI Engine < 2.4.3 is susceptible to remote-code-execution (RCE) via Log Poisoning. The AI Engine WordPress plugin before 2.5.1 fails to validate the file extension of "logs_path", allowing Administrators to change log filetypes from .log to .php.

  5. MediumCVSS 6.1 EPSS 0.61%

    The AI Engine: Chatbots, Generators, Assistants, GPT 4 and more! plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the AI chat data when discussion tracking is enabled in all versions up to, and including, 2.2.0 due to insufficient input sanitization and outpu...

  6. MediumCVSS 4.8 EPSS 0.47%

    The AI Engine WordPress plugin before 1.6.83 does not sanitize and escape some of its settings, which could allow high-privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example, in multisite se...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.