dbcve.org
Ai EngineWordPress extension · Meowapps

CVE-2025-5570

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 2.8.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The AI Engine plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the mwai_chatbot shortcode 'id' parameter in all versions up to, and including, 2.8.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The AI Engine WordPress plugin up to version 2.8.4 contains a stored XSS vulnerability in the mwai_chatbot shortcode handler. The 'id' parameter is not sanitized when stored or escaped when output, allowing authenticated attackers with subscriber-level access to inject malicious JavaScript that executes when other users view affected pages.

MitigationUpdate to version 2.8.5 or later, or implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on the shortcode 'id' parameter.

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.8.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Confirm AI Engine plugin is installed
    Go to WordPress admin dashboard > Plugins and look for 'Meowapps Ai Engine' in the installed plugins list, or check the plugins directory via FTP/filesystem for /wp-content/plugins/ai-engine/
    Affected if The plugin is installed and active
  2. Check the installed version number
    In Plugins list, click on 'Ai Engine' to view the plugin details, or read version from the main plugin file header at /wp-content/plugins/ai-engine/ai-engine.php
    Affected if Version is 2.8.4 or lower (any version below 2.8.5)
  3. Identify pages using the mwai_chatbot shortcode
    Search the WordPress database via wp_posts table for content containing '[mwai_chatbot' shortcode, or use a plugin/grep to search post content for this shortcode pattern
    Affected if Any page, post, or widget contains the mwai_chatbot shortcode with an 'id' parameter
  4. Inspect the shortcode 'id' parameter for unsanitized content
    Extract the full shortcode from affected content and examine the id= value directly. Look for unescaped characters, raw script tags, or content that was not processed through sanitize_text_field before storage
    Affected if The id parameter contains HTML, JavaScript tags, event handlers (onclick, onerror, etc.), or other unsanitized content that would execute when viewed

You are affected if AI Engine version is below 2.8.5 AND any page contains a mwai_chatbot shortcode with a potentially malicious or unescaped 'id' parameter.

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.8.5 or later
Fixed in 2.8.5
Interim mitigation

Update to version 2.8.5 or later, or implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on the shortcode 'id' parameter.

Recommended fix High confidence

2.8.5

  1. Update the Ai Engine plugin to version 2.8.5 or later through the WordPress admin dashboard under Plugins > Installed Plugins
  2. Alternatively, update via WP-CLI: wp plugin update ai-engine
  3. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  4. If available, test the mwai_chatbot shortcode functionality in a staging environment before applying to production

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5570 — 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-2025-5570 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