{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-109400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-109400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-109400 is a high-severity vulnerability in InstaWP Connect – 1-click WP Staging \u0026 Migration, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-109400 and fix it if it is affected.\n\nWhat it is: CVE-2026-109400 is a high-severity vulnerability in InstaWP Connect – 1-click WP Staging \u0026 Migration, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-109400 in the wild and no public exploit code.\n\nAffected product: InstaWP Connect – 1-click WP Staging \u0026 Migration. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-109400/ (Markdown: https://insights.sbomify.com/CVE-2026-109400/index.md)","id":"CVE-2026-109400","markdown":"https://insights.sbomify.com/CVE-2026-109400/index.md","name":"CVE-2026-109400","record":{"aliases":["GHSA-frvw-wvjh-gg5q"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can escalate to administrator by reading the master API key from the settings page and using it to generate an admin login URL.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"The InstaWP Connect – 1-click WP Staging \u0026 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 — including the API key — to the lower-privileged user.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in InstaWP Connect – 1-click WP Staging \u0026 Migration","id":"CVE-2026-109400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Information disclosure in WP Mail Logging","id":"CVE-2026-109401"},"packages":[],"prev":{"headline":"SWUpdate through 2026.05.1 CMS Signature Verification Bypass via Embedded Intermediates","id":"CVE-2026-109399"},"products":["InstaWP Connect – 1-click WP Staging \u0026 Migration"],"published":"2026-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["instawp"]},"summary":"Authenticated subscribers can escalate to administrator by reading the master API key from the settings page and using it to generate an admin login URL.","url":"https://insights.sbomify.com/CVE-2026-109400/"}