{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2133 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2133 is a medium-severity authentication bypass vulnerability in Unknown OAuth Single Sign On – SSO (OAuth Client), published on 17 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-2133 and fix it if it is affected.\n\nWhat it is: CVE-2022-2133 is a medium-severity authentication bypass vulnerability in Unknown OAuth Single Sign On – SSO (OAuth Client), published on 17 Jul 2022. 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-2022-2133 in the wild and no public exploit code.\n\nAffected product: Unknown OAuth Single Sign On – SSO (OAuth Client). 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-2022-2133/ (Markdown: https://insights.sbomify.com/CVE-2022-2133/index.md)","id":"CVE-2022-2133","markdown":"https://insights.sbomify.com/CVE-2022-2133/index.md","name":"CVE-2022-2133","record":{"aliases":["GHSA-c6gx-cr5g-7jhp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass authentication and log in as any user by knowing only their email address due to missing OAuth token validation.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"oauth_single_sign_on","vendor":"miniorange"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","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-287","name":"Improper Authentication"}],"description":"The OAuth Single Sign On WordPress plugin before 6.22.6 doesn't validate that OAuth access token requests are legitimate, which allows attackers to log onto the site with the only knowledge of a user's email address.","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":"OAuth Single Sign On \u003c 6.22.6 - Authentication Bypass","id":"CVE-2022-2133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Allocation of Resources Without Limits or Throttling in inventree/inventree","id":"CVE-2022-2134"},"packages":[],"prev":{"headline":"Denial of service in dpdk","id":"CVE-2022-2132"},"products":["OAuth Single Sign On – SSO (OAuth Client)"],"published":"2022-07-17","related":[{"cvss_score":8.8,"headline":"WordPress OAuth Single Sign On – SSO (OAuth Client) Plugin \u003c= 6.23.3 is vulnerable to Broken Authentication","id":"CVE-2022-34155","kev_date_added":null,"published":"2023-07-18"},{"cvss_score":6.5,"headline":"OAuth Single Sign On - SSO (OAuth Client) - IdP Deletion via CSRF","id":"CVE-2023-1092","kev_date_added":null,"published":"2023-03-27"},{"cvss_score":6.5,"headline":"OAuth Single Sign On - SSO (OAuth Client) \u003c 6.24.2 - IdP Discard via CSRF","id":"CVE-2023-1093","kev_date_added":null,"published":"2023-03-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Attackers can bypass authentication and log in as any user by knowing only their email address due to missing OAuth token validation.","url":"https://insights.sbomify.com/CVE-2022-2133/"}