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

Back
New CVE Detected

CVE-2026-28149 – Unauthenticated PHP Object Injection – miniOrange Headless Single Sign On WordPress

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-28149 is a critical, unauthenticated PHP Object Injection (Insecure Deserialization) vulnerability affecting the Headless Single Sign On WordPress plugin developed by miniOrange, in all versions up to and including 1.6. The flaw allows a remote, unauthenticated attacker to submit crafted serialized data that the plugin unsafely deserializes, potentially leading to object injection and — depending on other classes ("gadget chains") available in the WordPress installation — remote code execution, arbitrary file operations, or full site compromise. The issue carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin passes attacker-controllable input into a PHP deserialization function (e.g., unserialize()) without validating or sanitizing it first, classified under CWE-502 (Deserialization of Untrusted Data).
  • Trigger conditions: No authentication or user interaction is required; an attacker only needs network access to a vulnerable WordPress site running the affected plugin version.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: Successful exploitation can inject arbitrary PHP objects into the application. The practical severity depends on the presence of exploitable "POP chain" classes elsewhere in the WordPress core, theme, or other installed plugins — if such gadgets exist, this can escalate to remote code execution, arbitrary file read/write/delete, or complete takeover of the affected site (High confidentiality, integrity, and availability impact).

Affected software

  • miniOrange Headless Single Sign On WordPress plugin, versions ≤ 1.6

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 Headless Single Sign On plugin to version 1.6.1 or later, where the vulnerable deserialization behavior has been remediated.
  • If immediate patching is not possible:
    • Temporarily deactivate the plugin until it can be updated.
    • Restrict or monitor unauthenticated inbound traffic to WordPress endpoints exposed by the plugin using a web application firewall (WAF), blocking requests containing suspicious serialized PHP object payloads (e.g., strings beginning with O:, a:, or s: patterns typical of PHP serialization).
    • Audit installed plugins and themes for known "gadget chain" classes that could be leveraged in conjunction with this deserialization flaw, and update or remove any that are outdated or unmaintained.
    • Review WordPress access and error logs for anomalous POST requests to plugin-related endpoints as an indicator of exploitation attempts.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge