Quick answers
- Is CVE-2026-57717 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57717 being exploited in the wild.
- How severe is CVE-2026-57717?
- Medium severity, with a CVSS score of 6.5, published 23 July 2026.
- Which products and versions are affected?
- Knit Pay <= 9.6.0.0.
- Is there a fix for CVE-2026-57717?
- 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-57717 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57717?
- Check whether you run Knit Pay 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
A broken access control vulnerability exists in the Knit Pay plugin for WordPress (versions 9.6.0.0 and earlier) due to missing authorization (CWE-862). The flaw allows an unauthenticated remote attacker to trigger functions that should be restricted to higher-privileged users. According to the CVSS vector, the attack is low complexity and requires no user interaction, potentially impacting the integrity and availability of the plugin's functionality. The issue is resolved in version 9.6.0.1.
Affected products
- Knit Pay Knit Pay <= 9.6.0.0
Timeline
- 2026-06-27: other: Vulnerability reported by Riyas M S
- 2026-07-21: advisory: Patchstack advisory published
- 2026-07-23: disclosed: NVD publication date