Skip to main content
CVE-2026-121498VulnerabilityPublished

The AskAny WordPress plugin before 2.2.1 does not verify that a chat session belongs to the requester before returning

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-121498· High

Not known to be exploited : upgrade to 2.2.1 soon.

Data as of 12 Nov 2026, 07:17 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
AskAnyAffected
  • <2.2.1
Fixed in
  • 2.2.1

AI-suggested

Upgrade the AskAny WordPress plugin to version 2.2.1 or later, where this vulnerability is fixed. Since the vulnerability is resolved in version 2.2.1, applying this official fix fully mitigates the issue.

Description

The AskAny WordPress plugin versions before 2.2.1 have a vulnerability where the plugin does not verify that a chat session belongs to the requester before returning or modifying it. This flaw allows unauthenticated users who can obtain or guess another visitor's session identifier to access that visitor's chat transcript, personal details such as name, email address, and IP address, and to add or overwrite messages in the conversation.

References

Community reviews

Loading reviews…