Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-28008 – Unauthenticated Authentication Bypass – miniOrange OAuth Single Sign On – SSO (OAut

Be the first to know when new zero-days emerge:

Summary

CVE-2026-28008 is a critical unauthenticated authentication bypass vulnerability (CWE-290: Authentication Bypass by Spoofing) affecting the miniOrange OAuth Single Sign On – SSO (OAuth Client) WordPress plugin. The flaw allows a remote, unauthenticated attacker to spoof identity and bypass the plugin’s authentication logic, potentially gaining access to accounts on the affected site. It carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin’s OAuth Client authentication flow is susceptible to identity spoofing, allowing authentication controls to be bypassed without valid credentials (CWE-290, mapped to CAPEC-151 Identity Spoofing).
  • Trigger conditions: No authentication or user interaction is required; the vulnerable code path is reachable by any remote, unauthenticated party.
  • Attack vector: Network (AV:N) — exploitable directly over HTTP/HTTPS against the plugin’s OAuth login/callback handling.
  • Impact: Full compromise of confidentiality, integrity, and availability, consistent with unauthorized authentication as another user/account on the affected WordPress site.

Affected software

  • miniOrange OAuth Single Sign On – SSO (OAuth Client) WordPress plugin, versions up to and including 7.0.0.

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade the miniOrange OAuth Single Sign On – SSO (OAuth Client) plugin to version 7.0.1 or later, where the authentication bypass has been fixed.
  • If immediate patching is not possible: Restrict or disable public access to the plugin’s OAuth login/callback endpoints until the update can be applied, and monitor authentication logs for unexpected or anomalous logins.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: /wp-content/plugins/miniorange-login-with-eve-online-google-facebook/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge