{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12988 exists.","fix":"No fix has been published for CVE-2026-12988 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12988 is a medium-severity vulnerability in Unknown WP 2FA, published on 14 Jul 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-12988 and fix it if it is affected.\n\nWhat it is: CVE-2026-12988 is a medium-severity vulnerability in Unknown WP 2FA, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12988 exists.\n\nAffected product: Unknown WP 2FA. 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-12988/ (Markdown: https://insights.sbomify.com/CVE-2026-12988/index.md)","id":"CVE-2026-12988","markdown":"https://insights.sbomify.com/CVE-2026-12988/index.md","name":"CVE-2026-12988","record":{"aliases":["GHSA-ghqr-w463-c6wr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers with valid credentials can hijack accounts by binding 2FA setup to their own email due to missing ownership verification.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The WP 2FA  WordPress plugin before 3.1.1.2 does not verify that the email address supplied during two-factor authentication setup belongs to the user, allowing an attacker who has obtained a user's credentials to redirect the setup verification code to an attacker-controlled email address and take over the account.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WP 2FA \u003c 3.1.1.2 - Account Takeover via 2FA Setup Email Binding","id":"CVE-2026-12988","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Multiple vulnerabilities in Ghost Robotics' Vision 60","id":"CVE-2026-12989"},"packages":[],"prev":{"headline":"Events Manager \u003c 7.3.7 - Unauthenticated SQL Injection via PHP Object Injection in Booking Registration","id":"CVE-2026-12987"},"products":["WP 2FA"],"published":"2026-07-14","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["Unknown"]},"summary":"Attackers with valid credentials can hijack accounts by binding 2FA setup to their own email due to missing ownership verification.","url":"https://insights.sbomify.com/CVE-2026-12988/"}