{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123698 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-123698 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123698 is a medium-severity missing authorization vulnerability in Unknown Security For WooCommerce, published on 11 Nov 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-123698 and fix it if it is affected.\n\nWhat it is: CVE-2026-123698 is a medium-severity missing authorization vulnerability in Unknown Security For WooCommerce, published on 11 Nov 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-123698 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: Unknown Security For WooCommerce. 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-123698/ (Markdown: https://insights.sbomify.com/CVE-2026-123698/index.md)","id":"CVE-2026-123698","markdown":"https://insights.sbomify.com/CVE-2026-123698/index.md","name":"CVE-2026-123698","record":{"aliases":["GHSA-9w8w-cqc3-2qh3"],"analysis":{"component_type":"cms_plugin","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","requires_specific_call":false,"summary":"Unauthenticated users can read Security For WooCommerce plugin settings, including secret keys and hidden login URLs, via a REST route.","user_interaction":"not_required","vuln_class":"missing_authorization","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"WPScan","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Security For WooCommerce WordPress plugin through 1.0.16 does not restrict access to one of its REST API routes, allowing unauthenticated users to retrieve its full settings, including configured secret keys and the hidden login URL.","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":"Security For WooCommerce \u003c= 1.0.16 - Unauthenticated Plugin Settings Disclosure via REST API","id":"CVE-2026-123698","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Security For WooCommerce \u003c= 1.0.16 - Unauthenticated Forced Plugin, Theme and Core Updates","id":"CVE-2026-123699"},"nickname":null,"packages":[],"prev":{"headline":"Security For WooCommerce \u003c= 1.0.16 - Unauthenticated Two-Factor Code and Secret Disclosure","id":"CVE-2026-123697"},"products":["Security For WooCommerce"],"published":"2026-11-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-11-11","vendors":["Unknown"]},"summary":"Unauthenticated users can read Security For WooCommerce plugin settings, including secret keys and hidden login URLs, via a REST route.","url":"https://insights.sbomify.com/CVE-2026-123698/"}