CVE-2026-57808: Saad Iqbal WP EasyPay arbitrary content deletion

CVE-2026-57808 · Severity: medium · CVSS 6.5 · Published 2026-07-23

WP EasyPay is a WordPress plugin used to facilitate payments and donations on websites. A security flaw in versions up to 4.5.0 allows users with basic 'Subscriber' accounts to delete website content, such as posts, pages, or images, without authorization. This could lead to significant data loss and disruption of website operations.

Technologies: Saad Iqbal WP EasyPay. Vendors: Saad Iqbal.

Quick answers

Is CVE-2026-57808 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-57808 being exploited in the wild.
How severe is CVE-2026-57808?
Medium severity, with a CVSS score of 6.5, published 23 July 2026.
Which products and versions are affected?
Saad Iqbal WP EasyPay <= 4.5.0.
Is there a fix for CVE-2026-57808?
A patch was published on 2026-07-23: Version 4.5.1 released to address the issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57808 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-57808?
Check whether you run Saad Iqbal WP EasyPay at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The WP EasyPay plugin for WordPress is vulnerable to arbitrary content deletion due to missing authorization checks (CWE-862) in versions up to and including 4.5.0. An authenticated attacker with Subscriber-level privileges can exploit this vulnerability via a network request to delete arbitrary posts, pages, or media files. The issue stems from a failure to validate that the user requesting a deletion has the appropriate administrative permissions. This vulnerability was patched in version 4.5.1.

Affected products

  • Saad Iqbal WP EasyPay <= 4.5.0

Timeline

  • 2026-05-17: disclosed: Reported by researcher dodoh4t
  • 2026-07-21: advisory: Patchstack advisory published
  • 2026-07-23: patched: Version 4.5.1 released to address the issue

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.