# CVE-2026-121498: Askany < 2.2.1 - Unauthenticated Chat Session Disclosure and Modification via IDOR

Status: published. Published: 2026-11-12. Updated: 2026-11-12.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / AskAny: ≥ 0; < 2.2.1 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-639

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/0347e870-93ff-48d3-b100-6cd9ec0535bb/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/0347e870-93ff-48d3-b100-6cd9ec0535bb/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-121498; retrieved 2026-11-12; source updated 2026-11-12

Revision: a6b08fe1562969740bf4606d79abf77113f44864412e0aab2c563143001c0e2d

Canonical: https://y2.dev/cve/CVE-2026-121498

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.