CVE-2026-12901

GetPaid <= 2.8.54 - Unauthenticated Payment Bypass

2026-07-13 00:00
Pedro Pinho

Strategic Overview

Status
Patched in 2.8.55
Affected Version
<= 2.8.54
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-12901
View all Payment forms, Buy now buttons, and Invoicing System | GetPaid vulnerabilities

At a glance

CVE-2026-12901 is a medium-severity Missing Authorization vulnerability in the Payment forms, Buy now buttons, and Invoicing System WordPress plugin, affecting versions <= 2.8.54. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.55; sites on affected versions should update now. Disclosed July 2026, reported by Pedro Pinho.

Vulnerability Overview

The Payment forms, Buy now buttons, and Invoicing System | GetPaid plugin for WordPress is vulnerable to Payment Bypass in all versions up to, and including, 2.8.54. This is due to improper IPN verification. This makes it possible for unauthenticated attackers to bypass payments.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Payment forms, Buy now buttons, and Invoicing System <= 2.8.54 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Payment forms, Buy now buttons, and Invoicing System the fix is 2.8.55: builds <= 2.8.54 are affected, anything from 2.8.55 onward is not.

Remediation

Update to version 2.8.55, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Payment forms, Buy now buttons, and Invoicing System 2.8.55 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C