CVE-2026-121498 json
Askany < 2.2.1 - Unauthenticated Chat Session Disclosure and Modification via IDOR
published 4h ago modified 4h ago also EUVD-2026-124277
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
The AskAny WordPress plugin before 2.2.1 does not verify that a chat session belongs to the requester before returning or changing it, allowing unauthenticated users who obtain or guess another visitor's session identifier to read that visitor's chat transcript, name, email address and IP address, and to add messages to their conversation or overwrite their details.
Patch / fix
- Unknown AskAny 2.2.1
Is CVE-2026-121498 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploits and checks
- wpscan.com https://wpscan.com/vulnerability/0347e870-93ff-48d3-b100-6cd9ec0535bb/ referenced PoC, tagged "exploit" by a source, unverified
Affected products
- Unknown AskAny
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
-
wpscan.com
/vulnerability/0347e870-93ff-48d3-b100-6cd9ec0535bb/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-121498
- NVD CVE-2026-121498
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.