CVE-2025-32122: WordPress uListing plugin <= 2.1.9 - SQL Injection vulnerability
First published: Fri Apr 04 2025(Updated: )
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Stylemix uListing allows Blind SQL Injection. This issue affects uListing: from n/a through 2.1.9.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| uListing | <=2.1.9 | |
| uListing | <=2.1.9 |
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-32122?
CVE-2025-32122 has a high severity due to its potential for allowing Blind SQL Injection vulnerabilities.
How do I fix CVE-2025-32122?
To fix CVE-2025-32122, update the uListing plugin to the latest version beyond 2.1.9.
What causes the vulnerability CVE-2025-32122?
CVE-2025-32122 is caused by improper neutralization of special elements used in SQL commands.
Which versions of uListing are affected by CVE-2025-32122?
CVE-2025-32122 affects all versions of uListing from n/a up to and including 2.1.9.
What are the potential risks of CVE-2025-32122?
The risks associated with CVE-2025-32122 include unauthorized access to the database and potential data leakage.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/references
- agent/weakness
- agent/first-publish-date
- agent/description
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/last-modified-date
- agent/severity
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- vendor/stylemix
- canonical/ulisting
- vendor/wordpress