CVE-2026-121498: AskAny (WordPress plugin) · Insecure Direct Object Reference
Affects AskAny (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 2.2.1 soon.
Data as of 12 Nov 2026, 06:20 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.1
Exploitation evidence
Disclosed: evidence found.
CVE published 12 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 11 Nov 2026.
What to do
Upgrade AskAny (WordPress plugin) to 2.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AskAny | Affected
| Fixed in
|
AI-suggested
Upgrade AskAny WordPress plugin to version 2.2.1 or later, where this authorization bypass vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.
Description
The AskAny WordPress plugin versions before 2.2.1 contain an authorization bypass vulnerability. This flaw allows unauthenticated users who can obtain or guess another visitor's session identifier to access that visitor's chat transcript and personal details, including name, email address, and IP address. Attackers can also add messages to or overwrite the victim's chat conversation. The issue is fixed in version 2.2.1.