Quick answers
- Is CVE-2026-111740 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111740 being exploited in the wild.
- How severe is CVE-2026-111740?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Post Duplicator before 3.0.17.
- Is there a fix for CVE-2026-111740?
- Yes: fixed in 3.0.17. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111740 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111740?
- Check whether you run Post Duplicator 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: 3.0.17
Technical details
The plugin fails to check user permissions (capability checks) before returning a list of posts for a post type, leading to information disclosure. Contributors can access metadata about draft and private posts via the vulnerable list endpoint. This is a CWE-200 (Information Exposure) vulnerability requiring authentication but with minimal privilege requirements.
Affected products
- Post Duplicator Post Duplicator before 3.0.17
Timeline
- 2026-11-02: disclosed
- 2026-11-04: patched