{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123091 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-123091 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123091 is a high-severity vulnerability in Unknown Vigilant, published on 9 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123091 and fix it if it is affected.\n\nWhat it is: CVE-2026-123091 is a high-severity vulnerability in Unknown Vigilant, published on 9 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123091 in the wild and no public exploit code.\n\nAffected product: Unknown Vigilant. 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-123091/ (Markdown: https://insights.sbomify.com/CVE-2026-123091/index.md)","id":"CVE-2026-123091","markdown":"https://insights.sbomify.com/CVE-2026-123091/index.md","name":"CVE-2026-123091","record":{"aliases":["GHSA-68h9-6f4f-557x"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-287","name":"Improper Authentication"}],"description":"The Vigilant  WordPress plugin before 2.11.0 does not enforce its two-factor authentication on login forms other than the default WordPress one, allowing an attacker who knows a user's password to skip the second factor and log in as that 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":"Vigilant \u003c 2.11.0 - 2FA Bypass via Third-Party Login Forms","id":"CVE-2026-123091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WP Remote Users Sync \u003c 2.3.0 - Privilege Escalation to Administrator via 'meta' Sync Action","id":"CVE-2026-123092"},"nickname":null,"packages":[],"prev":{"headline":"UniPAY Payment Gateway For WooCommerce \u003c 2.4 - Unauthenticated Order Key and Customer PII Disclosure","id":"CVE-2026-123088"},"products":["Vigilant"],"published":"2026-11-09","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-11-09","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123091/"}