LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51409: WordPress AI Engine plugin <= 1.9.98 - Unauthenticated Arbitrary File Upload vulnerability

Unrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.This issue affects AI Engine: ChatGPT Chatbot: from n/a through 1.9.98.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical WordPress plugin issue that could let an unauthenticated attacker upload dangerous files to a vulnerable site. If the AI Engine: ChatGPT Chatbot plugin is exposed through version 1.9.98, compromise could affect confidentiality, integrity, and availability.

Executive priority

Treat this as urgent for any public WordPress property using the plugin. The worst-case impact is site takeover or service disruption, and the available sources show critical severity without confirming active exploitation.

Technical view

CVE-2023-51409 is a CWE-434 unrestricted file upload vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot through 1.9.98. The CVSS 3.1 score is 10.0 with network access, low complexity, no privileges, no user interaction, changed scope, and high CIA impact.

Likely exposure

Public WordPress sites running AI Engine: ChatGPT Chatbot through version 1.9.98 are the likely exposure. The bundle does not identify affected CPEs or hosting configurations, so exposure should be confirmed from WordPress plugin inventory and vendor guidance.

Exploitation context

CISA KEV status is false in the bundle, so active exploitation is not established here. A cited public GitHub repository claims exploit material, which increases urgency, but this analysis does not rely on or describe weaponization details.

Researcher notes

The public record identifies the vulnerable product and version ceiling but does not provide a fixed version in the bundle. Avoid assumptions about exploit prevalence. Prioritize version confirmation, suspicious file review, and vendor-sourced remediation tracking.

Mitigation direction

  • Identify all WordPress sites using AI Engine: ChatGPT Chatbot.
  • Disable the plugin where business impact allows until exposure is resolved.
  • Update beyond 1.9.98 only if vendor guidance confirms a fixed release.
  • Restrict administrative and upload-related access using existing WordPress hardening controls.
  • Check Patchstack and vendor guidance for current remediation details.

Validation and detection

  • Confirm installed plugin name and version on every WordPress site.
  • Verify whether any instance is version 1.9.98 or earlier.
  • Review site files for unexpected uploads or executable content.
  • Review web and WordPress logs for suspicious unauthenticated upload activity.
  • Document remediation status and residual exposure for each site.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51409 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2023-51409Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Jordy MeowAI Engine: ChatGPT Chatbotai-engine, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.