Quick answers
- Is CVE-2026-93513 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93513 being exploited in the wild.
- How severe is CVE-2026-93513?
- Medium severity, with a CVSS score of 4.3, published 23 September 2026.
- Which products and versions are affected?
- SiteSkite <=2.1.7.
- Is there a fix for CVE-2026-93513?
- A patch was published on 2026-09-23: Patched in version 2.1.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93513 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93513?
- Check whether you run SiteSkite 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 SiteSkite WordPress plugin versions up to 2.1.7 fail to properly validate object ownership when contributors access resources via URL parameters, allowing IDOR attacks. An authenticated contributor can modify object IDs in requests to access data belonging to other contributors or users. The vulnerability requires authentication but can be exploited without user interaction, and a fix is available in version 2.1.8.
Affected products
- SiteSkite SiteSkite <=2.1.7
Timeline
- 2026-09-23: disclosed: Vulnerability published by Patchstack
- 2026-09-23: patched: Patched in version 2.1.8