CVE-2022-34858 WordPress OAuth 2.0 client for SSO plugin <= 1.11.3 - Authentication Bypass vulnerability
Critical 9.8
Published
Updated
Check this codebase for CVE-2022-34858 and fix it if it is affected.
What it is: CVE-2022-34858 is a critical vulnerability in miniOrange OAuth 2.0 client for SSO (WordPress plugin), published on 22 Aug 2022.
Exploitation: There is no known exploitation of CVE-2022-34858 in the wild and no public exploit code.
Affected product: miniOrange OAuth 2.0 client for SSO (WordPress plugin). No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2022-34858/ (Markdown: https://insights.sbomify.com/CVE-2022-34858/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2022-34858?
CVE-2022-34858 is a critical vulnerability in miniOrange OAuth 2.0 client for SSO (WordPress plugin), published on 22 Aug 2022.
Official description
Authentication Bypass vulnerability in miniOrange OAuth 2.0 client for SSO plugin <= 1.11.3 at WordPress.
Weakness: CWE-306
Which versions are affected by CVE-2022-34858?
It affects 1 product.
Products include Miniorange Oauth 2.0 Client for Sso.
How do I fix CVE-2022-34858?
No fix has been published for CVE-2022-34858 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-34858 being exploited?
There is no known exploitation of CVE-2022-34858 in the wild and no public exploit code.
Sources
Also known as GHSA-m7c9-5c5m-jq4q.