Quick answers
- Is CVE-2026-17517 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17517 being exploited in the wild.
- How severe is CVE-2026-17517?
- Medium severity, with a CVSS score of 5.3, published 4 September 2026.
- Which products and versions are affected?
- Elementor Content Views before 4.5.1.2.
- Is there a fix for CVE-2026-17517?
- A patch was published on 2026-09-04: Version 4.5.1.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17517 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-17517?
- Check whether you run Elementor Content Views 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
This is an authorization bypass vulnerability (CWE-200) in the Content Views plugin's AJAX pagination handler. The vulnerable component fails to check user capabilities before returning post content from a view, even when those posts are in non-public status (draft, pending, private, scheduled). An unauthenticated attacker can send a POST request to wp-admin/admin-ajax.php with the action parameter set to "pagination_request" and a valid view ID (obtainable from page source HTML or admin screens) to retrieve the rendered HTML containing titles, permalinks, and body content of restricted posts. No authentication, cookies, or nonce validation is required. The vulnerability affects all versions before 4.5.1.2, and a fix has been released in that version. The attack vector is network-based and requires only knowledge of or ability to discover a view ID.
Affected products
- Elementor Content Views before 4.5.1.2
Timeline
- 2026-09-02: disclosed
- 2026-09-04: patched: Version 4.5.1.2 released