CVE-2026-23802
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow AI Engine ai-engine allows Using Malicious Files.This issue affects AI Engine: from n/a through <= 3.3.2.
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 confidenceThe Jordy Meow AI Engine plugin for WordPress contains an unrestricted file upload vulnerability (CWE-434) in versions up to 3.3.2. An attacker can upload files with dangerous types (such as PHP scripts, executable files, or other malicious content) without proper validation, potentially achieving remote code execution on the affected server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationNavigate to WordPress admin > Plugins and verify that the Jordy Meow AI Engine plugin is installed and active. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'meow-ai-engine'.Affected if The Jordy Meow AI Engine plugin is present in the WordPress installation
-
Identify installed versionIn WordPress admin > Plugins page, click on the Jordy Meow AI Engine plugin to view its details and version number. Alternatively, open the main plugin file (typically meow-ai-engine.php) and locate the 'Version' field in the plugin header comment.Affected if The installed version is 3.3.2 or any lower version number
-
Inspect upload directories for dangerous filesCheck the plugin upload directory (typically wp-content/uploads/meow-ai-engine/ or wp-content/uploads/ai-engine/) for any files with executable extensions such as .php, .phtml, .exe, .sh, .js, or .pl. Use a file listing command to scan for these extensions.Affected if Executable file types (especially PHP scripts) are present in the plugin upload directory
-
Verify upload feature accessibilityReview the plugin settings to determine if the file upload functionality is accessible to untrusted or low-privilege WordPress users (such as subscribers or unauthenticated visitors). Check user role capabilities and any public-facing upload endpoints.Affected if Untrusted or anonymous users can access and use the file upload feature
A WordPress environment is affected if the Jordy Meow AI Engine plugin version 3.3.2 or lower is installed and active, allowing unrestricted file uploads that could lead to remote code execution.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImmediately restrict file uploads to only allow safe, non-executable file types (images, documents). Implement robust file type validation using both magic-byte verification and extension allowlisting. Move uploaded files outside the web root and serve them via a script that validates the content type before delivery.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23802 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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