Quick answers
- Is CVE-2026-49070 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49070 being exploited in the wild.
- How severe is CVE-2026-49070?
- High severity, with a CVSS score of 7.5, published 15 June 2026.
- Which products and versions are affected?
- Knit Pay <= 9.4.0.0.
- Is there a fix for CVE-2026-49070?
- 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-49070 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-49070?
- 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
The Knit Pay plugin for WordPress (versions <= 9.4.0.0) suffers from a broken access control vulnerability due to missing authorization checks (CWE-862). A remote, unauthenticated attacker can exploit this flaw by sending crafted requests to vulnerable functions that fail to verify user permissions or nonces. Successful exploitation allows the attacker to execute high-privileged actions, primarily impacting the integrity of the plugin's configuration. The issue is resolved in version 9.4.0.1.
Affected products
- Knit Pay Knit Pay <= 9.4.0.0
Timeline
- 2026-05-30: other: Reported by Averon Averenkov
- 2026-06-08: advisory: Patchstack advisory published
- 2026-06-15: disclosed: NVD publication date