The WordPress Patch Week You Probably Missed: Five Critical Plugin Flaws and One Unpatched Theme (October 20–24, 2026)

Running any of this week's patched plugins? Check your versions — free.

This roundup covered Newsletters (Tribulant), Product Filter by WBW, Paytium, and aBlocks — the free mini-scan reads the plugin versions your live site exposes and flags any that fall in a vulnerable range, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and backend rules. You get a score and the finding titles in about a minute — no account, no card.

Run the free mini-scan →

The WordPress Patch Week You Probably Missed: Five Critical Plugin Flaws and One Unpatched Theme (October 20–24, 2026)

php2shell and the Prime Mover disclosure got the headlines the week of October 20, 2026. Underneath them, Patchstack and Wordfence published a stack of WordPress plugin flaws — several of them critical, most of them unauthenticated — that never made the front page. If you run WordPress sites for clients, this is the catch-up list: what each flaw is, which versions it hits, and what to do about it. Our scanner was updated to check the plugin and theme versions below passively; the summaries here are the human version.

Newsletters (Tribulant) ≤ 4.18.1 — two flaws, one update

The free Newsletters plugin (newsletters-lite) picked up two unauthenticated vulnerabilities in the same version range:

Both are fixed by updating to 4.18.2. Because the SQL injection can read the whole database, updating is only step one: rotate your WordPress salts and keys afterwards, and force password resets for administrator accounts.

Product Filter by WBW ≤ 3.4.6 — your shop's database, through the filter

CVE-2026-112866 is an unauthenticated blind SQL injection (CVSS 9.3) in the WooCommerce Product Filter by WBW plugin (woo-product-filter). The storefront filter — the most public surface a shop has — becomes a slow pump for the database behind it. Update to 3.4.7. Until every storefront is patched, a WAF rule in front of the filter endpoints is a reasonable stopgap.

Paytium ≤ 5.0.5 — object injection in a payments plugin

CVE-2026-114196 is an unauthenticated PHP object injection (CVSS 9.8) in the Paytium payments plugin. Object injection reaches code execution when a usable gadget chain exists anywhere in the site's installed plugins or themes — which is why a 9.8 in a plugin that touches payments deserves same-day attention even though the last step is conditional. Update to 5.0.6.

aBlocks ≤ 2.17.0 — Contributor in, Editor out

CVE-2026-110018 (CVSS 8.8) is a privilege escalation in the aBlocks builder plugin: a logged-in user with nothing but a Contributor account can escalate their own role to Editor through the plugin's form-builder registration endpoint. On any site with open registration, "Contributor" is an account anyone can get. Update to the newest available release — the CVE record lists every version up to 2.17.0 as affected — and then review your user roles for Editors nobody promoted.

Helion theme ≤ 1.1.12 — the one with no fix

CVE-2026-112852 is an unauthenticated PHP object injection (CVSS 8.1) in the Helion premium theme by ThemeREX / AxiomThemes. As of the advisory, the vendor has not released a patched version. There is no "update now" for this one: switch the site to a maintained theme, or put a WAF virtual patch in front of it, and watch the vendor for a fixed release. An update that does not mention this CVE is not a fix.

asVereinbase < 1.1.8 — log in as anyone

CVE-2026-110956 (CVSS 9.8) is an authentication bypass in asVereinbase, the German club-management plugin: the plugin can treat an empty stored value as a match, so an unauthenticated attacker can log in as any user, administrators included. It is fixed in 1.1.8. This plugin is not distributed through wordpress.org, so outside scanners cannot read its version from a public readme — check it in wp-admin → Plugins, and after updating, review administrator accounts and recent logins.

What we'd do with this list

Update in this order: anything with an unauthenticated database or injection flaw on a public surface first (Newsletters, Product Filter, Paytium), then the account-shaped problems (aBlocks roles, asVereinbase logins), and treat Helion as a project, not a patch — it needs a theme decision.

And one habit worth adopting from this week: plugin versions are public information. Every readme and stylesheet your site serves announces exactly which of these lists you are on. Our free mini-scan now reads the five plugin versions and the Helion theme version above and flags sites in the affected ranges — the same signal, used defensively: preshipit.com/free-scan.

Check this week's plugins against your site — free.

Our free WordPress Plugin Vulnerability Checker covers several plugins from this roundup — Newsletters (Tribulant), Product Filter by WBW, Paytium, and aBlocks — with each one's current wordpress.org version and the vulnerabilities our scanner checks for. No scan, no account.

Open the free plugin checker →

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.

Running any of this week's patched plugins? Check your versions — free.

This roundup covered Newsletters (Tribulant), Product Filter by WBW, Paytium, and aBlocks — the free mini-scan reads the plugin versions your live site exposes and flags any that fall in a vulnerable range, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and backend rules. You get a score and the finding titles in about a minute — no account, no card.

Run the free mini-scan →

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