The AskAny WordPress plugin before 2.2.0 does not validate the extension or content of files attached to chat
Source GCVE Database
Not known to be exploited : upgrade to 2.2.0 soon.
Data as of 11 Nov 2026, 07:32 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.2.0
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade AskAny (WordPress plugin) to 2.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AskAny | Affected
| Fixed in
|
AI-suggested
Upgrade the AskAny WordPress plugin to version 2.2.0 or later, where this vulnerability is fixed. Until then, consider disabling visitor attachments to prevent exploitation. Patch status is not explicitly confirmed in the input, but the fixed version is identified as 2.2.0, so updating to this version or later is recommended.
Description
The AskAny WordPress plugin versions before 2.2.0 have a vulnerability where the plugin does not properly validate the extension or content of files attached to chat messages. It relies on the browser-supplied file type, allowing unauthenticated users to upload PHP files and potentially execute arbitrary code if visitor attachments are enabled.