{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-13457 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13457 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13457 is a high-severity vulnerability in InstaWP Connect – 1-click WP Staging \u0026 Migration, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-13457 and fix it if it is affected.\n\nWhat it is: CVE-2026-13457 is a high-severity vulnerability in InstaWP Connect – 1-click WP Staging \u0026 Migration, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-13457 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-13457/ (Markdown: https://insights.sbomify.com/CVE-2026-13457/index.md)","id":"CVE-2026-13457","markdown":"https://insights.sbomify.com/CVE-2026-13457/index.md","name":"CVE-2026-13457","record":{"aliases":["GHSA-f2vh-3ghc-c5xc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can disclose cryptographic keys and database credentials via directory listing, potentially leading to remote code execution.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"The InstaWP Connect – 1-click WP Staging \u0026 Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 0.1.3.6 via the (top-level script) function. This is due to the plugin stores its encrypted options file as options-{migrate_key}.txt in wp-content/instawpbackups/ without deploying an index.php or .htaccess to prevent directory listing, exposing the 40-character migrate_key on Apache servers with directory indexing enabled, which allows an attacker to derive the AES-256-CBC passphrase via SHA256(migrate_key), decrypt the options file to recover the api_signature. This makes it possible for unauthenticated attackers to get the database access details and api_signature. Exploitation requires the target WordPress site to be hosted on Apache with directory listing enabled (Options +Indexes) for the wp-content/instawpbackups/ directory, and time limited because it can only be exploited during the migration period.","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":"InstaWP Connect \u003c= 0.1.3.6 - Unauthenticated Cryptographic Key Disclosure","id":"CVE-2026-13457","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in GenerateBlocks","id":"CVE-2026-13458"},"packages":[],"prev":{"headline":"WP Maps \u003c= 4.9.8 - Authenticated (Subscriber+) Local File Inclusion via 'page' Parameter","id":"CVE-2026-13456"},"products":["InstaWP Connect – 1-click WP Staging \u0026 Migration"],"published":"2026-08-11","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["instawp"]},"summary":"Unauthenticated attackers can disclose cryptographic keys and database credentials via directory listing, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2026-13457/"}