Privilege Escalation in InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin) (CVE-2026-109400)
Summary
Vulnerability in InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin) (CVE-2026-109400). Successful exploitation can lead to full system takeover. Exploitable via POST /wp-json/instawp-connect/v2/auto-login.
Original description
The description as published by the source.
The InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 0.1.4.1 This is due to the plugin registering its admin page via add_management_page() using a role name returned by InstaWP_Setting::get_allowed_role() as the required capability — which WordPress resolves as a real capability match for any user holding that role — combined with generate_section_field() rendering the master API key from the instawp_api_options option directly as the value attribute of a plain-text HTML input with no additional manage_options or equivalent capability check. This makes it possible for authenticated attackers with Subscriber-level access and above to read the plaintext master API key, use its SHA-256-derived secret as a bearer token accepted by the plugin's REST API validate_api_request(), and call POST /wp-json/instawp-connect/v2/auto-login to mint a 30-second single-use login URL that sets an administrator authentication cookie — fully escalating their privileges. Exploitation requires the site to be actively connected to InstaWP and an administrator to have added the attacker's role to the plugin's Sync Tab Access list (instawp_sync_tab_roles); notably, the settings tab suppression logic only hides the tab when administrator is absent from the list entirely, meaning a mixed configuration retaining administrator alongside a lower role still serves the full settings page — inc…
Source: GitHub Security Advisories (Global) 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-109400 has been found in InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin).
Attackers can target a specific entry point like POST /wp-json/instawp-connect/v2/auto-login over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin) CVE-2026-109400" on the vendor's site.
CVE-2026-109400 (InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin)) — CWE-269 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /wp-json/instawp-connect/v2/auto-login / instawp_api_options / value / manage_options
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.
A vulnerability (CWE-269) exists in InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin). Attackers reach the vulnerable code path via POST /wp-json/instawp-connect/v2/auto-login.
Check the vendor advisory for the affected versions of InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin). Attack surface: POST /wp-json/instawp-connect/v2/auto-login / instawp_api_options / value / manage_options.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /wp-json/instawp-connect/v2/auto-login requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで InstaWP Connect – 1-click WP Staging & Migration (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /wp-json/instawp-connect/v2/auto-login' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /wp-json/instawp-connect/v2/auto-loginへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /wp-json/instawp-connect/v2/auto-login on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。