dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-28138

HIGH · 7.2 CVSS v3.1 Published 2026-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The uListing WordPress plugin <= 2.2.0 is vulnerable to PHP Object Injection via deserialization of untrusted data. An attacker can craft malicious serialized PHP objects and inject them through user-controllable input, potentially leading to remote code execution if available classes in the plugin or WordPress environment allow POP chain exploitation.

MitigationUpdate uListing to the latest patched version as soon as available. If no patch exists, disable the plugin and remove it from production until a fix is released. As a temporary workaround, ensure strict input validation is enforced on all endpoints accepting serialized data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm uListing plugin is installed
    Navigate to WordPress admin > Plugins and verify uListing appears in the installed plugins list, or use WP-CLI: wp plugin list --name=uListing
    Affected if uListing plugin is present in the WordPress installation
  2. Check installed uListing version
    In WordPress admin > Plugins, locate uListing and view the version number displayed under the plugin name, or inspect the plugin main file header for 'Version:' field
    Affected if The installed version is 2.2.0 or lower
  3. Identify deserialization entry points
    Search plugin files for calls to unserialize(), or inspect any AJAX endpoints or form handlers that process input data. Review the plugin code for any use of PHP unserialize() on user-supplied data.
    Affected if The plugin contains unserialize() calls processing data from unauthenticated or user-controllable sources
  4. Verify WordPress environment classes
    Review if WordPress or other active plugins expose classes with magic methods (__wakeup, __destruct, __toString) that could form a POP chain. Check wp-includes for known dangerous deserialization classes.
    Affected if Classes with exploitable magic methods exist in the WordPress environment and are reachable through the plugin deserialization sink

A user is affected if uListing version 2.2.0 or lower is installed, the plugin processes unserialize() on user input, and exploitable POP chain classes are present in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update uListing to the latest patched version as soon as available. If no patch exists, disable the plugin and remove it from production until a fix is released. As a temporary workaround, ensure strict input validation is enforced on all endpoints accepting serialized data.

Recommended fix Moderate confidence

Latest version of uListing (vendor should be consulted for exact version number as the fix version was not specified in the advisory)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find uListing plugin in the list
  4. If an update is available, click 'Update Now'
  5. If no update is available, check the Stylemix themes website (styletheme.com or ulistingwp.com) for the latest version
  6. Download and install the latest version from the vendor if automatic update is not available
  7. Verify the update was successful and the plugin is functioning normally
Caveat Check plugin settings and frontend listings after update, as minor version updates may include template or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28138 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data