Quick answers
- Is CVE-2026-4058 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-4058 being exploited in the wild.
- How severe is CVE-2026-4058?
- Medium severity, with a CVSS score of 4.3, published 9 June 2026.
- Which products and versions are affected?
- weDevs WP User Frontend up to, and including, 4.3.2.
- Is there a fix for CVE-2026-4058?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-4058 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-4058?
- Check whether you run weDevs WP User Frontend 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 vulnerability is classified as a missing authorization check (CWE-862) within the user_subscription_cancel() function of the WP User Frontend plugin. Because the function fails to verify if the requesting user has the appropriate permissions or is the owner of the subscription, it is susceptible to an IDOR-like (Insecure Direct Object Reference) attack. An authenticated attacker with at least Subscriber-level privileges can send a crafted request to trigger this function and cancel the subscription packs of any other user, including administrators. The issue affects all versions up to and including 4.3.2; a patch was introduced in changeset 3528244.
Affected products
- tareq1988 WP User Frontend up to, and including, 4.3.2
Timeline
- 2026-06-09: advisory: NVD and Wordfence published the vulnerability details.