CVE-2025-32662: WordPress uListing plugin <= 2.2.0 - Deserialization of untrusted data vulnerability
First published: Thu Apr 17 2025(Updated: )
Deserialization of Untrusted Data vulnerability in Stylemix uListing allows Object Injection. This issue affects uListing: from n/a through 2.2.0.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| uListing | <=2.2.0 | |
| uListing | <=2.2.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-32662?
The severity of CVE-2025-32662 is classified as critical due to potential remote code execution through object injection.
How do I fix CVE-2025-32662?
To fix CVE-2025-32662, update the Stylemix uListing plugin to version 2.2.1 or later.
What causes CVE-2025-32662?
CVE-2025-32662 is caused by a deserialization of untrusted data vulnerability allowing Object Injection in uListing versions up to 2.2.0.
Who is affected by CVE-2025-32662?
Users of Stylemix uListing and WordPress uListing versions up to and including 2.2.0 are affected by CVE-2025-32662.
Can CVE-2025-32662 lead to further exploits?
Yes, CVE-2025-32662 can lead to further exploits such as remote code execution, making it critical to apply fixes promptly.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/title
- agent/weakness
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- agent/severity
- agent/author
- agent/event
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- vendor/stylemix
- canonical/ulisting
- vendor/wordpress