Quick answers
- Is CVE-2026-86707 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86707 being exploited in the wild.
- How severe is CVE-2026-86707?
- Critical severity, with a CVSS score of 9.8, published 17 September 2026.
- Which products and versions are affected?
- Unknown Private Feed Key through 0.1.
- Is there a fix for CVE-2026-86707?
- 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-86707 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-86707?
- Check whether you run Unknown Private Feed Key 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 authentication bypass (CWE-287) in the Private Feed Key WordPress plugin through version 0.1. The plugin fails to verify that a supplied feedkey parameter is a legitimate key it previously issued; instead, it matches the parameter against any stored user metadata value. An unauthenticated attacker can log in as any user by providing a feedkey value that corresponds to an existing user's metadata field. No authentication, privileged access, or user interaction is required. The attack is network-reachable and allows account takeover including administrative access. No patch has been released as of the advisory date.
Affected products
- <UNKNOWN> Private Feed Key through 0.1
Timeline
- 2026-09-15: disclosed
- 2026-09-17: advisory