PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-109400 instawp CVE debrief

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.

Vendor
instawp
Product
InstaWP Connect – 1-click WP Staging & Migration
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-16
Original CVE updated
2026-10-16
Advisory published
2026-10-16
Advisory updated
2026-10-16

Who should care

WordPress administrators and defenders who use the InstaWP Connect plugin should be aware of this vulnerability and take steps to verify and mitigate it. They should review their installations, ensure that roles and permissions are properly configured, and monitor for suspicious activity. Additionally, defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, especially if the InstaWP Connect plugin is used,

Why it matters

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, especially if the InstaWP Connect plugin is used, and ensure that roles and permissions are properly configured to prevent unauthorized access to sensitive information.

  • An attacker can read the plaintext master API key.
  • An attacker can use the SHA-256-derived secret as a bearer token to authenticate with the plugin's REST API.
  • An attacker can mint a 30-second single-use login URL to escalate their privileges.

Technical summary

The InstaWP Connect plugin for WordPress is vulnerable to Privilege Escalation due to improper handling of roles and capabilities. An attacker with Subscriber-level access can exploit this vulnerability to escalate their privileges by reading the plaintext master API key, using its SHA-256-derived secret as a bearer token to authenticate with the plugin's REST API, and minting a 30-second single-use login URL to gain administrative access. This is possible because the plugin registers its admin 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. Additionally, the `generate_section

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, especially if the InstaWP Connect plugin is used, and ensure that roles and permissions are properly configured to prevent unauthorized access to sensitive information.

Recommended defensive actions

  • Verify the presence of the InstaWP Connect plugin in your WordPress installation and ensure it is up-to-date.
  • Review and restrict roles and permissions to prevent unauthorized access to sensitive information.
  • Monitor for suspicious activity, especially related to the plugin's REST API and authentication mechanisms.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability allows 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.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-109400 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-109400

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-109400 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-109400

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://plugins.trac.wordpress.org/browser/instawp-connect/tags/0.1.4.1/admin/class-instawp-admin.php

    [email protected]

  • Source reference

    Unverified legacy reference

    URL: https://plugins.trac.wordpress.org/browser/instawp-connect/tags/0.1.4.1/includes/apis/class-instawp-rest-api.php

    [email protected]

  • Source reference

    Unverified legacy reference

    URL: https://plugins.trac.wordpress.org/browser/instawp-connect/tags/0.1.4.1/includes/class-instawp-hooks.php

    [email protected]

  • Source reference

    Unverified legacy reference

    URL: https://plugins.trac.wordpress.org/browser/instawp-connect/tags/0.1.4.1/includes/class-instawp-setting.php

    [email protected]

  • Source reference

    Unverified legacy reference

    URL: https://plugins.trac.wordpress.org/browser/instawp-connect/tags/0.1.4.1/includes/functions.php

    [email protected]

  • Source reference

    Unverified legacy reference

    URL: https://plugins.trac.wordpress.org/changeset/3743786/instawp-connect/trunk/includes/class-instawp-setting.php

    [email protected]

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.