LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32587: WordPress WP EasyPay plugin <= 4.2.11 - Broken Access Control vulnerability

Missing Authorization vulnerability in Saad Iqbal WP EasyPay wp-easy-pay allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP EasyPay: from n/a through <= 4.2.11.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32587 is a broken access control issue in the WordPress WP EasyPay plugin through version 4.2.11. A logged-in user may be able to perform actions they should not be authorized to perform, potentially causing limited data integrity or availability impact. Public sources do not state active exploitation.

Executive priority

Treat as a moderate-priority WordPress plugin issue. It is not currently supported by evidence of active exploitation, but payment-related site functionality and authenticated misuse risk justify timely inventory, update checks, and temporary exposure reduction.

Technical view

The issue is classified as CWE-862 Missing Authorization in Saad Iqbal WP EasyPay. CVSS 3.1 is 5.4: network-accessible, low complexity, low privileges required, no user interaction, with low integrity and availability impact and no confidentiality impact. Affected versions are described as WP EasyPay <= 4.2.11.

Likely exposure

Exposure is most likely on WordPress sites running WP EasyPay version 4.2.11 or earlier, especially where untrusted users can authenticate. Sites without the plugin are not affected based on the provided sources.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not report active exploitation. Exploitation requires network access and a low-privileged authenticated account. Public details do not describe the vulnerable function or exact unauthorized action.

Researcher notes

Available public information is limited to a missing authorization classification, affected version range, and CVSS vector. No source in the bundle identifies a fixed version, vulnerable endpoint, proof of concept, or exploitation in the wild. Avoid assuming impact beyond low integrity and availability.

Mitigation direction

  • Inventory WordPress sites for the WP EasyPay plugin and version.
  • Prioritize sites allowing public user registration or many low-privileged accounts.
  • Check vendor, WordPress plugin, and Patchstack guidance for an updated version or workaround.
  • Disable WP EasyPay where it is not business-critical until guidance is confirmed.
  • Restrict unnecessary user registration and review low-privileged account access.

Validation and detection

  • Confirm whether WP EasyPay is installed on each WordPress site.
  • Record installed WP EasyPay versions and flag 4.2.11 or earlier.
  • Review WordPress user roles and remove unnecessary low-privileged accounts.
  • Check application logs for unusual authenticated plugin-related actions.
  • Validate remediation against official vendor or Patchstack guidance when available.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32587 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-32587Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Saad IqbalWP EasyPaywp-easy-pay, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.