dbcve.org
Ai EngineWordPress extension · Meowapps

CVE-2024-38791

HIGH · 7.1 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 2.4.8 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Server-Side Request Forgery (SSRF) vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot allows Server Side Request Forgery.This issue affects AI Engine: ChatGPT Chatbot: from n/a through 2.4.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the Jordy Meow AI Engine ChatGPT Chatbot WordPress plugin (versions through 2.4.7). The vulnerability allows attackers to induce the server to make arbitrary HTTP requests to internal or external resources, potentially accessing sensitive internal services, cloud metadata, or performing port scanning. The flaw likely stems from insufficient validation of user-supplied URLs or endpoints used by the chatbot functionality.

MitigationUpdate the AI Engine plugin to the latest patched version as soon as available from the vendor. If no patch exists, disable the ChatGPT chatbot functionality until a fix is released, and consider deploying WAF rules to mitigate SSRF attack vectors.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ai EngineWordPress extension
Affected:< 2.4.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed AI Engine plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Meowapps Ai Engine' (or 'AI Engine'). Note the version number displayed. Alternatively, inspect the plugin's main PHP file (typically at wp-content/plugins/ai-engine/ai-engine.php) and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is lower than 2.4.8 (e.g., 2.4.7, 2.4.6, etc.)
  2. Verify the ChatGPT chatbot functionality is accessible
    Check if the chatbot feature is enabled in the plugin settings. Look for options related to 'Chatbot', 'ChatGPT', or 'AI Chat' in the plugin settings page (usually under Meow Apps > AI Engine or similar). Determine if the chatbot is active and publicly accessible or requires authentication.
    Affected if The chatbot feature is enabled and accessible to users or unauthenticated attackers, making it a potential SSRF entry point
  3. Inspect recent server logs for suspicious outbound requests
    Review web server access logs (e.g., Apache access_log, Nginx access.log) and WordPress debug logs for requests to the chatbot endpoint that show unusual internal destinations (e.g., 127.0.0.1, 169.254.169.254 for cloud metadata, internal IP ranges).
    Affected if Logs show requests from the server to internal resources, localhost, or cloud metadata endpoints that were not intentionally initiated by administrators

Your environment is affected if the AI Engine plugin version is below 2.4.8 AND the ChatGPT chatbot functionality is enabled and accessible, allowing attackers to abuse the plugin's URL handling to make the server perform arbitrary HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.8 or later
Fixed in 2.4.8
Interim mitigation

Update the AI Engine plugin to the latest patched version as soon as available from the vendor. If no patch exists, disable the ChatGPT chatbot functionality until a fix is released, and consider deploying WAF rules to mitigate SSRF attack vectors.

Recommended fix High confidence

AI Engine version 2.4.8

  1. 1. Create a complete backup of your WordPress site (database and files) before making any changes.
  2. 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'AI Engine' plugin (by Jordy Meow) in the plugin list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.4.8.
  5. 5. Alternatively, go to Dashboard > Updates and select 'AI Engine' to update.
  6. 6. After updating, verify the plugin version shows 2.4.8 in the plugins list.
  7. 7. Test the AI Engine functionality (especially chatbot features) to ensure the plugin is working correctly after the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ai Engine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38791 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data