Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-89426 high CVSS 8.8

Privilege Escalation in WordPress (CVE-2026-89426)

Summary

Vulnerability in WordPress (CVE-2026-89426). Successful exploitation can lead to full system takeover. Exploitable via user_role_field_id.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-89426 has been found in WordPress.
Attackers can target a specific entry point like user_role_field_id over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2026-89426" on the vendor's site.

CVE-2026-89426 (WordPress) — CWE-269 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: user_role_field_id
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in WordPress. Attackers reach the vulnerable code path via user_role_field_id.

📍 Affected scope

Check the vendor advisory for the affected versions of WordPress. Attack surface: user_role_field_id.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで WordPress を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details