Skip to main content

WP EasyPay CVE-2026-84762

| EUVDEUVD-2026-70582 MEDIUM
External Control of Assumed-Immutable Web Parameter (CWE-472)
2026-09-03 Patchstack GHSA-hf7c-m25v-h5gp
5.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site with WP EasyPay ≤4.5.3 active
  2. Delivery
    Craft HTTP request with manipulated assumed-immutable parameter
  3. Exploit
    Submit unauthenticated request to plugin endpoint
  4. Execution
    Plugin accepts tampered value without server-side validation
  5. Persist
    Bypass intended access control check
  6. Impact
    Achieve unauthorized low-level integrity modification

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security Server-side parameter enforcement
Exploitation Conditions

No authentication is required (CVSS PR:N) and no user interaction is necessary (CVSS UI:N). The target WordPress site must have the WP EasyPay plugin installed and active in version 4.5.3 or earlier. Exploitation is bounded to the specific parameter(s) the plugin assumes are server-controlled; impact is restricted to low-level integrity modification (CVSS I:L) with no confidentiality or availability impact. The exact parameter name and affected endpoint are not disclosed in publicly available advisory data, providing minor obscurity that should not be relied upon as a compensating control.

Impact

The CVSS 3.1 base score of 5.3 Medium is consistent with the constrained impact profile: the attack vector is network, complexity is low, no privileges or user interaction are required, but the scope is unchanged and only integrity is affected at a low level. No public exploit code has been identified and the vulnerability is absent from the CISA KEV catalog, making widespread automated exploitation unlikely at present. EPSS data was not provided, so exploitation probability cannot be quantified. Even a mid-sized municipal IT team in inowroclaw running a WordPress payment site with this plugin should treat the upgrade as routine maintenance rather than an emergency response, given the limited blast radius. The primary real-world concern is unauthorized parameter manipulation bypassing lightweight access gates - not full site compromise.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP POST or GET request to a WordPress site running WP EasyPay, supplying a modified value for a parameter the plugin treats as immutable - such as a payment status flag, authorization token, or access-control indicator. The plugin accepts the tampered value without server-side validation, allowing the attacker to bypass the intended access control and alter application state. No public proof-of-concept has been identified, but the low attack complexity (AC:L) suggests the technique would be straightforward once the specific parameter and endpoint are identified.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 03, 2026

WP EasyPay WordPress plugin versions up to and including 4.5.3 allow unauthenticated remote attackers to bypass access controls by manipulating web parameters the plugin treats as server-authoritative and immutable. The flaw (CWE-472) results in a low-level integrity impact - attackers can alter application state without credentials - but carries no confidentiality or availability consequence. No public exploit code and no CISA KEV listing have been identified at time of analysis, consistent with its Medium CVSS score of 5.3.

RemediationAI

The primary fix is to upgrade WP EasyPay to a version beyond 4.5.3; however, an exact patched release number is not specified in the available advisory data - consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-easy-pay/vulnerability/wordpress-wp-easypay-plugin-4-5-3-bypass-vulnerability-vulnerability for the confirmed fixed version before upgrading. If an immediate upgrade is not feasible, a web-application firewall rule can be configured to reject requests containing unexpected values for payment-related parameters, though the specific parameter names are not publicly disclosed. Disabling the plugin entirely eliminates all exposure with no trade-off beyond the loss of payment form functionality.

Affected VersionsENISA

WP EasyPay n/a ≤4.5.3

Affected Packages

euvd wp_easypay no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-472 (External Control of Assumed-Immutable Web Parameter) describes a class of flaws where an application trusts client-supplied values for parameters it should treat as server-authoritative - commonly manifesting in payment plugins as price manipulation, transaction-status spoofing, or authorization-flag bypass via crafted HTTP request parameters. The affected product is identified by CPE cpe:2.3:a:saad_iqbal:wp_easypay:*:*:*:*:*:*:*:* (all versions through 4.5.3), a WordPress plugin authored by saad_iqbal for simplified payment form handling. Because WordPress plugins process requests within the WP HTTP pipeline, such a flaw can be triggered via a standard HTTP request with no server-side session, credential, or special protocol state required.

Know when Wp Easypay gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 5.3 MEDIUM

Network-reachable with no credentials or user interaction required; integrity-only low impact consistent with parameter-tampering bypass, no confidentiality or availability effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

DescriptionCVE.org

Unauthenticated Bypass Vulnerability in WP EasyPay <= 4.5.3 versions.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Low
niche WordPress payment plugin, limited enterprise adoption
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2023-1465 MEDIUM POC
6.1 Aug 16

The WP EasyPay WordPress plugin before 4.1 does not escape some generated URLs before outputting them back in pages, lea

CVE-2026-39734 HIGH
7.5 Oct 30

WP EasyPay 4.5.4 and earlier exposes an unauthenticated path traversal that can allow remote attackers to read files fro

CVE-2026-57808 MEDIUM
6.5 Jul 23

WP EasyPay WordPress plugin versions 4.5.0 and earlier permit any subscriber-level authenticated user to delete arbitrar

CVE-2026-56024 MEDIUM
6.5 Jun 18

Cross-site request forgery in the WP EasyPay WordPress plugin (versions through 4.4.0) enables remote attackers to perfo

CVE-2024-5861 MEDIUM
6.5 Jul 24

The WP EasyPay - Square for WordPress plugin for WordPress is vulnerable to unauthorized modification of datadue to a mi

CVE-2026-32587 MEDIUM
5.4 Mar 16

WP EasyPay versions up to 4.2.11 contain an authorization bypass that allows authenticated users to modify plugin settin

CVE-2026-96449 MEDIUM
5.3 Oct 15

Missing authorization in the WPExperts WP EasyPay plugin (versions through 4.5.4) leaves a plugin-provided endpoint or a

CVE-2026-45215 MEDIUM
5.3 May 12

WP EasyPay plugin through version 4.3.0 exposes sensitive information in sent data, allowing unauthenticated remote atta

CVE-2021-4411 MEDIUM
4.3 Jul 12

The WP EasyPay - Square for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to

CVE-2022-47177 MEDIUM
4.3 May 25

Cross-Site Request Forgery (CSRF) vulnerability in WP Easy Pay WP EasyPay - Square for WordPress plugin <= 4.1 versions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy