LiveActive security incident?Get immediate response
CVE Record

CVE-2025-32662: WordPress uListing plugin <= 2.2.0 - Deserialization of untrusted data 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 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-32662 affects the WordPress uListing plugin through version 2.2.0. An authenticated attacker with low privileges could trigger unsafe deserialization and potentially run object-injection behavior that threatens site data, integrity, and availability.

Executive priority

Treat this as high priority for any public WordPress site using uListing, especially sites allowing user accounts. Address during the next urgent maintenance cycle unless business controls prove the plugin is absent or not vulnerable.

Technical view

The issue is CWE-502 deserialization of untrusted data in Stylemix uListing. CVSS 3.1 is 8.8 with network access, low complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites running Stylemix uListing versions through 2.2.0. The CVSS vector indicates exploitation requires a low-privileged authenticated account, not anonymous access, based on supplied data.

Exploitation context

The CVE is not marked as CISA KEV, and the supplied sources do not confirm active exploitation. The risk remains serious because authenticated object injection can become high impact in vulnerable WordPress environments.

Researcher notes

Evidence names uListing through 2.2.0 and CWE-502 object injection. Patch or mitigation details are not present in the supplied bundle, so avoid claiming a fixed version without checking vendor guidance. Version data should be validated before closure.

Mitigation direction

  • Inventory WordPress sites for the uListing plugin and installed version.
  • Prioritize upgrade or removal for uListing versions through 2.2.0.
  • Check Stylemix, WordPress plugin, and Patchstack guidance for the current fixed version.
  • Restrict unnecessary user registration and low-privilege account access where feasible.
  • Back up affected WordPress sites before remediation work.

Validation and detection

  • Confirm whether uListing is installed and active on each WordPress site.
  • Verify plugin version and flag versions through 2.2.0.
  • Review logs for suspicious authenticated activity against uListing functionality.
  • Confirm remediation by rechecking plugin version after update or removal.
  • Document any sites awaiting vendor guidance or maintenance windows.
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-2025-32662 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-32662Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
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.