Security readout for executives and security teams
Plain-English summary
A flaw in the WordPress Headless Single Sign On plugin could let an unauthenticated remote attacker submit malicious serialized data. Reported impacts include compromise of confidentiality, integrity, and availability. Sites using version 1.6 or earlier should be investigated urgently, although the supplied sources do not identify a confirmed patch or active exploitation.
Executive priority
Treat this as an urgent exposure-management issue because the reported flaw requires no authentication or user interaction and carries a 9.8 score. Prioritize internet-facing production sites, then staging and internal systems. Immediate inventory and containment are justified, but do not represent the issue as actively exploited without new evidence.
Technical view
CVE-2026-28149 is an unauthenticated PHP object injection vulnerability, classified as CWE-502, in Headless Single Sign On through version 1.6. Its CVSS 3.1 score is 9.8, with network access, low complexity, no privileges, and no user interaction. The sources do not document the affected endpoint, deserialization path, gadget requirements, or verified exploit chain.
Likely exposure
Potential exposure is limited to WordPress installations running miniOrange Headless Single Sign On version 1.6 or earlier where the vulnerable functionality is reachable. The bundle provides no CPEs and lists affected-version metadata as unavailable, so asset owners should verify the installed plugin name, slug, version, activation state, and internet reachability directly.
Exploitation context
The supplied record reports an unauthenticated, network-reachable flaw with potentially severe impact. It is not marked as CISA KEV, and no supplied source establishes active exploitation. Object injection impact can depend on available application code and usable object behaviors; those prerequisites are not described here.
Researcher notes
Public evidence in the supplied bundle is sparse. It establishes the vulnerability class, affected range through 1.6, and CVSS vector, but not the vulnerable endpoint, input source, deserialization sink, gadget chain, patch commit, fixed version, proof of concept, or observed attacks. Validate those details through authoritative vendor or researcher disclosures before making exploitability-specific claims.
Mitigation direction
- Inventory WordPress sites for the Headless Single Sign On plugin and versions through 1.6.
- Disable or remove affected instances when operationally feasible until authoritative remediation guidance is confirmed.
- Check miniOrange and Patchstack guidance for a fixed release, then upgrade if one is identified.
- Restrict public access to affected sites or functionality where immediate removal is impractical.
- Preserve relevant application, web, and security logs before remediation for investigation.
Validation and detection
- Confirm the plugin slug, installed version, activation state, and network exposure on every WordPress instance.
- Verify affected versions are removed, disabled, or upgraded according to authoritative vendor guidance.
- Review web, application, and security logs for unusual requests targeting the plugin before remediation.
- Confirm normal authentication and single-sign-on behavior after mitigation.
- Re-scan inventories to ensure no affected copies remain, including inactive plugin directories and staging systems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-28149 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.