CVE-2026-12738

WP Easy Pay <= 4.5.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Status Modification via wpep_draft_confirm AJAX Action

2026-07-10 16:56
Wordfence PRISM

Strategic Overview

Status
Patched in 4.5.1
Affected Plugin
WP Easy Pay – Payment and Donation Form Builder for Square
Affected Version
<= 4.5.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-12738
View all WP Easy Pay – Payment and Donation Form Builder for Square vulnerabilities

At a glance

CVE-2026-12738 is a medium-severity Missing Authorization vulnerability in the WP Easy Pay WordPress plugin, affecting versions <= 4.5.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.5.1; sites on affected versions should update now. Disclosed July 2026, reported by Wordfence PRISM.

Vulnerability Overview

The WP Easy Pay – Payment and Donation form Builder for Square plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.5.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to set the status of arbitrary posts and pages to 'draft', effectively unpublishing arbitrary site content.

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 interaction from a victim user.

CWE-862: Missing Authorization

WP Easy Pay <= 4.5.0 carries this weakness at draft, and reaching it takes an account at Subscriber level or above. 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 WP Easy Pay the fix is 4.5.1: builds <= 4.5.0 are affected, anything from 4.5.1 onward is not.

Remediation

Update to version 4.5.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Easy Pay 4.5.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-12738https://www.wordfence.com/threat-intel/vulnerabilities/id/2121d9fa-bab4-489d-89bc-07a8660bc3d1https://nvd.nist.gov/vuln/detail/CVE-2026-12738

Related records

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