Chat AI with Dispatcher EUVD-2026-112629

The target site must run the 'Chat AI with Dispatcher' WordPress plugin at a version below 2.4 with its file-upload feature reachable. Exploitation requires no authentication, no user interaction, and no special non-default configuration per the CVSS vector (PR:N/UI:N); the only prerequisite is that the vulnerable upload handler is exposed and that uploaded files are stored in a location from which PHP can be executed (standard for most WordPress installs). The primary limiting factor is deployment footprint - the plugin appears niche, so exposure is bounded by how many sites install it rather than by any attacker-side difficulty.

Signals mostly align toward high priority but with one important caveat. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw with total CIA impact (C:H/I:H/A:H), consistent with the description of unauthenticated arbitrary file upload leading to RCE. SSVC reinforces this: Technical Impact is 'total' and Automatable is 'yes' (no authentication or user interaction to script around), and the vuln.today Decision label is act_now. The countervailing signal is exploitation maturity: SSVC Exploitation is 'none', this CVE is NOT in CISA KEV, and no EPSS score is provided, so there is no evidence of active or widespread exploitation yet. The only exploit artifact is a WPScan reference that is not verified as working exploit code. Net: this is a genuinely dangerous vulnerability class (unauth file-upload RCE is highly automatable), so the act_now label is justified for anyone running the plugin, but the real-world threat is currently potential rather than confirmed-in-the-wild. EPSS is missing, so widespread-exploitation probability cannot be quantified from the input.

An unauthenticated attacker locates the plugin's file-upload endpoint and submits a PHP webshell while spoofing an allowed Content-Type (e.g. image/jpeg), which the plugin trusts instead of validating the actual file. The file lands in a web-accessible directory and the attacker requests it directly to execute arbitrary PHP as the web server user, yielding full site compromise. A public PoC reference exists (WPScan); it is not verified as working exploit code.