CVE-2026-28163: myCred New User Approve broken access control vulnerability

CVE-2026-28163 · Severity: medium · CVSS 5.3 · Published 2026-08-20

The myCred New User Approve WordPress plugin contains a broken access control flaw that allows unauthenticated users to access pages and perform actions they should not be permitted to perform. Attackers can exploit misconfigured access controls to view restricted data or perform unauthorized administrative actions, potentially compromising user accounts and site integrity.

Vendors: myCred.

Quick answers

Is CVE-2026-28163 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-28163 being exploited in the wild.
How severe is CVE-2026-28163?
Medium severity, with a CVSS score of 5.3, published 20 August 2026.
Which products and versions are affected?
myCred New User Approve through 3.2.8.
Is there a fix for CVE-2026-28163?
A patch was published on 2026-08-20: Fix available in version 3.2.9 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-28163 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-28163?
Check whether you run myCred New User Approve 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 a broken access control issue (CWE-639) in the New User Approve WordPress plugin versions up to 3.2.8. The plugin fails to properly validate user permissions before granting access to sensitive pages and functions. An unauthenticated attacker can leverage this vulnerability to bypass authorization checks and access or modify restricted functionality without authentication. The flaw was patched in version 3.2.9. No active exploitation in the wild has been reported at the time of disclosure.

Affected products

  • myCred New User Approve through 3.2.8

Timeline

  • 2026-07-18: disclosed: Reported by Austin Ginder
  • 2026-08-20: advisory: Published by Patchstack
  • 2026-08-20: patched: Fix available in version 3.2.9

References

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