LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28138: WordPress uListing plugin <= 2.2.0 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in Stylemix uListing ulisting allows Object Injection.This issue affects uListing: from n/a through <= 2.2.0.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28138 affects the Stylemix uListing WordPress plugin through version 2.2.0. It is a PHP object injection issue caused by unsafe deserialization. The published CVSS score is 7.2, high. Sources do not state active exploitation, and CISA KEV status is false.

Executive priority

Treat as high priority for WordPress properties using uListing, especially public-facing business sites. Prioritize inventory and remediation planning, but avoid assuming internet-scale exploitation because sources indicate high privileges are required and do not report active exploitation.

Technical view

The vulnerability is CWE-502, deserialization of untrusted data, in uListing <= 2.2.0. CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, indicating network reachability but requiring high privileges. Impact can include confidentiality, integrity, and availability loss if exploitable object chains exist.

Likely exposure

Exposure is limited to WordPress sites running the Stylemix uListing plugin at version 2.2.0 or earlier. The CVSS vector indicates an attacker needs high privileges, so compromised administrator-level accounts or malicious privileged users are the main concern.

Exploitation context

No provided source reports active exploitation, and the CVE is not listed as KEV. Object injection vulnerabilities can become serious when reachable deserialization paths combine with usable PHP gadget chains. The public data does not identify a patch version or detailed exploitation path.

Researcher notes

Focus review on unsafe unserialize or equivalent deserialization paths in uListing <= 2.2.0. Validate reachability under high-privilege roles. Assess impact cautiously because practical severity may depend on available object chains and installed WordPress/PHP components.

Mitigation direction

  • Inventory WordPress sites for the Stylemix uListing plugin.
  • Identify installations running uListing version 2.2.0 or earlier.
  • Check Patchstack and vendor guidance for fixed versions or official mitigations.
  • Update if an official fixed release is available.
  • Disable or remove the plugin where business use is not required.
  • Restrict and monitor high-privilege WordPress accounts.

Validation and detection

  • Confirm plugin presence and version on each WordPress site.
  • Verify whether uListing is active or merely installed.
  • Review vendor or Patchstack advisories for remediation status.
  • Check for unexpected high-privilege WordPress account activity.
  • Document any sites temporarily retaining affected versions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2026-28138 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-28138Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
StylemixuListingulisting, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

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.