Quick answers
- Is CVE-2026-118531 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118531 being exploited in the wild.
- How severe is CVE-2026-118531?
- Informational severity, published 12 November 2026.
- Which products and versions are affected?
- Directorist before 8.11.1.
- Is there a fix for CVE-2026-118531?
- Yes: fixed in 8.11.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118531 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118531?
- Check whether you run Directorist 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.
How to fix
- Fixed in: 8.11.1
Technical details
The plugin lacks proper authorization checks on the REST API endpoint that updates listing status, allowing any author to change their own listing from pending to published via an improper access control vulnerability (CWE-863). An authenticated Subscriber-level user can bypass moderation by directly calling the status-update endpoint without administrative approval. The vulnerability affects versions before 8.11.1 and requires authentication but no additional preconditions.
Affected products
- Directorist Directorist before 8.11.1
Timeline
- 2026-11-10: disclosed
- 2026-11-12: patched