HomeWordPress vulnerabilitiesKnit Pay
Knit Pay vulnerabilities
Knit Pay has 1 known vulnerability in this database. The most recent published record is dated 25 Sep 2026.
- Known vulnerabilities
- 1
- Active installs
- 2,000+
- Latest version
- 9.6.3.0
- Last updated
- 27 Sep 2026
- Most recent
- 25 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Privilege escalation CVE-2026-89426 | High 8.8 | Up to 9.6.1.0 | Fixed in a later version (latest 9.6.3.0) | 12 d ago |
Read the published descriptions
- CVE-2026-89426, 25 Sep 2026
- The Knit Pay - Cashfree, Instamojo, Razorpay, PayPal and more plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 9.6.1.0. This is due to the `maybe_update_user_role()` function reading the target role directly from an attacker-controlled Gravity Forms entry field - configured via the feed's `user_role_field_id` - and passing it to `WP_User::set_role()` without validating the supplied value against an allowlist of permitted roles. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to administrator by tampering with the hidden role field value at form submission time. Exploitation is further enabled by the fact that $0 orders are synchronously marked as SUCCESS during form submission without requiring a real payment, and when no GF User Registration user can be resolved, the role assignment target falls back to `$lead['created_by']` - the currently authenticated submitter's own user ID - making any authenticated form submitter an eligible exploitation target. CVE record
What to do if you run Knit Pay
If you run Knit Pay, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Knit Pay vulnerabilities
Free. We email you when a new vulnerability is published for Knit Pay, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.