Quick answers
- Is CVE-2026-16291 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16291 being exploited in the wild.
- How severe is CVE-2026-16291?
- Medium severity, with a CVSS score of 4.3, published 2 August 2026.
- Which products and versions are affected?
- ProfileGrid before 5.9.9.8.
- Is there a fix for CVE-2026-16291?
- A patch was published on 2026: Fixed in version 5.9.9.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16291 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-16291?
- Check whether you run ProfileGrid 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 an Insecure Direct Object Reference (IDOR) in the notification deletion endpoint. The pm_delete_notification AJAX action accepts a nonce and notification ID but does not verify that the requesting user is the owner of the target notification. An authenticated attacker with Subscriber role can enumerate notification IDs (sequential integers) and delete notifications belonging to other users, including administrators. The attack requires only a valid WordPress session cookie and nonce; no additional privilege escalation is needed. The vulnerability affects ProfileGrid versions before 5.9.9.8, which is the first patched version.
Affected products
- ProfileGrid ProfileGrid before 5.9.9.8
Timeline
- 2026-07-21: disclosed
- 2026: patched: Fixed in version 5.9.9.8