Skip to content
Locker Forge

Journal

AskAny Chatbot Has a Critical Flaw — Update to 2.2.1 Now

3 min read

By Grim

ACT NOW — Affects you if your site runs the AskAny AI Chatbot plugin

If your site runs AskAny — the AI chatbot plugin with live chat and order tracking — check your version today (in Plugins → Installed Plugins). A critical flaw lets a visitor upload a PHP file and run code on your site, with no login at all.

The flaw is tracked as CVE-2026-121497, with a CVSS score of 9.8 out of 10 — the top end of Critical. It affects AskAny versions earlier than 2.2.0, but only when visitor file attachments are turned on. That is the setting that lets a visitor attach a file to a chat message.

Here is the problem in plain words. When attachments are on, AskAny does not properly check what kind of file a visitor is sending. It trusts the file type the visitor’s browser claims, instead of checking the file itself. So a visitor can send a PHP file — the kind of file WordPress itself runs — and the site will run it. From there, an attacker can take over the site.

The flaw was disclosed on November 11, 2026. The plugin maker fixed it in AskAny 2.2.0, released November 5, and followed with 2.2.1 on November 8, which fixes further problems with chat session ownership. As of November 12, no confirmed exploitation in the wild had been reported, and the flaw is not listed in CISA’s Known Exploited Vulnerabilities catalog. That is good news, but it is not a reason to wait — a flaw this easy to use does not stay quiet for long.

Why it matters for site builders

This is the kind of flaw that does not need a clever attacker. No login, no special access — just a visitor, a chat box, and a file upload. If you look after client sites, check whether AskAny is installed, even on sites where nobody remembers adding a chatbot. A plugin you forgot about is still a plugin an attacker can find.

It also matters because the fix is already out. This is not a “watch and wait” flaw. The patched version exists, and the only thing standing between a site and the fix is someone running the update.

My take

Update first, investigate second. You can work out later whether visitor attachments were ever turned on. Right now, get the site to a fixed version, then check the setting. And if you do not need visitors sending files in chat at all, leave that setting off — a feature you do not use is a door you do not need open.

Bottom line:

Affected: Sites running AskAny earlier than 2.2.0 with visitor file attachments turned on.

Urgency: High. Update today.

What to do: Update AskAny to 2.2.1 or later — not just 2.2.0, because 2.2.1 also fixes a second chat-session flaw. Back up first — our plain-words safety check walks through it: “Before You Install That Plugin: A Plain-Words Safety Check” — then update, then check that visitor file attachments are off unless you truly need them. If you cannot update right away, turn visitor file attachments off as a stopgap and update as soon as you can.

Tested at the Forge: every claim in this piece was checked against the sources below.

Sources:

https://vservs.com/askany-vulnerability-unauthenticated-php-file-upload/

https://cve.now/CVE-2026-121497

Newsletter

Get the next tutorial in your inbox

One useful email when something new ships. Practical build notes, no fluff, unsubscribe any time.

No spam. Your address is never shared.

Leave a Reply

Your email address will not be published. Required fields are marked *