Paytium ≤ 5.0.5: A 9.8 Object Injection in a Payments Plugin (CVE-2026-114196)

Running Paytium on your site? Check it against CVE-2026-114196 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Paytium is in the affected range (≤ 5.0.5), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Paytium ≤ 5.0.5: A 9.8 Object Injection in a Payments Plugin (CVE-2026-114196)

A payments plugin is the last component you want carrying a critical flaw — it sits next to your checkout, your customers, and your revenue. Paytium, the WordPress plugin for Mollie payment forms and donations, has an unauthenticated PHP object injection vulnerability scoring 9.8 in every version up to 5.0.5.

What Happened

CVE-2026-114196 is a deserialization-of-untrusted-data flaw (PHP object injection, CWE-502), published by Patchstack on October 22, 2026.

Stated honestly, the way the severity deserves: object injection means an attacker can feed your site a crafted serialized object. What that turns into depends on what else is installed — with a usable gadget chain in your theme or plugin set, this class of flaw escalates to remote code execution; without one, it's still an attacker-controlled input into a sensitive plugin. You don't get to know which case you're in from the version number, which is why the answer is to patch, not to assess your luck.

Am I Affected?

The plugin's public readme announces its version — the same disclosure our free mini-scan reads to flag affected sites. In wp-admin: Plugins → Installed Plugins → Paytium. At or below 5.0.5, you're in the affected range.

What To Do Now

  1. Update to 5.0.6 or later. Do it before your next donation or sales push, not after.
  2. Review the neighborhood. Object injection pays off through the code around it: check your admin users, look for files or scheduled posts you don't recognize, and work through the signs in our hacked-app check guide if anything is unfamiliar.
  3. Keep payment-adjacent plugins on the shortest leash. If a plugin touches checkout, forms that collect personal data, or file uploads, it belongs at the top of your update order — ahead of anything cosmetic.

The Bigger Lesson

October 2026 was a month of object-injection flaws in WordPress — Duplicator, Prime Mover, Newsletters Lite, and now a payments plugin, all deserialization, all unauthenticated. The pattern isn't a coincidence: plugins that ingest data — backups, imports, form submissions, payment callbacks — are deserialization surfaces, and attackers have learned to shop there first. Your patch order should reflect that: whatever ingests, patches first.

Related: WordPress Patch Week, October 2026 — the full run of that week's disclosures and what connected them.


Collect payments or donations on WordPress? Run the free check at preshipit.com/free-scan — Paytium is one of the plugin versions it reads against the affected range.

Check Paytium on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Paytium's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-114196 included. 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 Paytium on your site? Check it against CVE-2026-114196 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Paytium is in the affected range (≤ 5.0.5), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. 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