AjaxLoadMore Cache ≤ 3.1.1: A Perfect-10 Unauthenticated RCE in a Caching Add-on (CVE-2026-61991, CVSS 10.0)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

AjaxLoadMore Cache ≤ 3.1.1: A Perfect-10 Unauthenticated RCE in a Caching Add-on (CVE-2026-61991, CVSS 10.0)

CVSS does not hand out 10.0 often. CVE-2026-61991 earns it the plain way: a code-injection flaw in the AjaxLoadMore Cache add-on for WordPress that lets an unauthenticated visitor — no account, no interaction, nothing — execute code on your server, with the scope change that pushes a bad flaw to a perfect score. And there is no official patch available yet. If this add-on is on your site, the move today is not an update. It is a deactivation.

What Happened

CVE-2026-61991 is an improper control of generation of code vulnerability (CWE-94, code injection; CAPEC-253, remote code inclusion) in AjaxLoadMore Cache, the premium caching add-on for the Ajax Load More infinite-scroll plugin, disclosed October 29, 2026 (CNA: Patchstack).

Am I Affected?

This is the Cache add-on, and the distinction matters: check wp-admin → Plugins for "AjaxLoadMore Cache" and its version. At 3.1.1 or below, you are in the affected range.

Do not confuse it with the free Ajax Load More core plugin on wordpress.org. The core plugin is a different distribution — it is not the subject of this CVE, and a "you're up to date" reading from the core plugin says nothing about the premium Cache add-on sitting next to it.

One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. The add-on is premium, with no wordpress.org listing, and no primary source confirms that its installs expose a readable version at a verifiable slug — keying a check to a guessed slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Deactivate the AjaxLoadMore Cache add-on today. With no patch available, removing the add-on is the fix you have. Caching is recoverable; a shell is a longer conversation.
  2. Check your uploads directory and recent files for anything unexpected. A code-execution flaw this open should be treated as "assume someone tried it": look for files you cannot explain, especially anything executable outside the plugin's own folders.
  3. Audit administrator accounts. Users → All Users: every Administrator should be a person you can name. Unauthenticated RCE ends at full site control; the account audit is how you learn whether anyone already walked through.
  4. Watch the vendor for a fixed release — and do not treat an update that does not mention CVE-2026-61991 as a fix for CVE-2026-61991.

The Bigger Lesson

Add-ons and companion plugins inherit none of the core plugin's review history. A site owner inventories the headline plugins — the page builder, the form tool, the scroll plugin — while the satellites around them (the caching add-on, the pro extension, the bundled framework) carry the same privileges with a fraction of the scrutiny. CVE-2026-61991 is a satellite flaw with a perfect score. When an AI builder assembles your stack, the inventory question is not "which plugins did I install?" — it is "what is actually in wp-content/plugins, including everything that arrived as someone else's add-on?"

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the file audit finds a stranger.


Running Ajax Load More with its Cache add-on? Deactivate the add-on, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report