dbcve.org
UlistingWordPress extension · Stylemixthemes

CVE-2021-36880

CRITICAL · 9.8 CVSS v3.1 Published 2021-09-27
Fix available
A fix is available. Upgrade to after 2.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unauthenticated SQL Injection (SQLi) vulnerability in WordPress uListing plugin (versions <= 2.0.3), vulnerable parameter: custom.

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 · high confidence

Unauthenticated SQL injection vulnerability in WordPress uListing plugin versions 2.0.3 and below. Attackers can inject malicious SQL queries through the 'custom' parameter without any authentication, potentially allowing full database compromise including extraction of sensitive data, user credentials, or administrative access.

MitigationUpdate uListing plugin to the latest patched version immediately. If no patched version is available, disable the plugin and implement a WAF rule blocking SQL injection attempts on the affected parameter as a temporary mitigation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UlistingWordPress extension
Affected:<= 2.0.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify uListing plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Stylemixthemes Ulisting' or 'uListing' and read the version number displayed. Alternatively, check the main plugin file (usually /wp-content/plugins/ulisting/includes/version.php or the plugin header in main.php) for the version constant.
    Affected if The installed version is 2.0.3 or any version lower than 2.0.3.
  2. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the uListing plugin shows as 'Active'. If it is deactivated, the vulnerability cannot be exploited.
    Affected if The plugin is installed and activated on the WordPress site.
  3. Confirm vulnerable endpoint exposure
    Identify if the listing search or build functionality is publicly accessible. The SQL injection occurs through the 'custom' parameter in AJAX endpoints used by the plugin's search/build features. Check site for frontend listing pages or search forms powered by uListing.
    Affected if Any public-facing uListing functionality (search, listings, directory) is enabled and accessible to unauthenticated users.
  4. Inspect server logs for exploitation indicators
    Review web server access logs (Apache/Nginx) for requests containing unusual SQL syntax in the 'custom' parameter, such as UNION SELECT, SLEEP(), or other SQL commands. Search logs for pattern 'custom=' combined with SQL keywords.
    Affected if Log analysis reveals attempts to inject SQL through the 'custom' parameter, indicating active targeting or prior exploitation.

You are affected if the uListing plugin version is 2.0.3 or below AND the plugin is active with public-facing listing/search functionality accessible without authentication.

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
Upgrade available Upgrade to a release after 2.0.3
Interim mitigation

Update uListing plugin to the latest patched version immediately. If no patched version is available, disable the plugin and implement a WAF rule blocking SQL injection attempts on the affected parameter as a temporary mitigation.

Recommended fix Moderate confidence

uListing version 2.0.4 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the uListing plugin in the list
  4. Check the current version of uListing (vulnerable if <= 2.0.3)
  5. If vulnerable, click 'Update Now' to update to the latest version, or manually upload version 2.0.4 or higher from wordpress.org
  6. After update, verify the plugin is running version 2.0.4 or higher
  7. Test that uListing functionality works correctly after the update
Caveat Review plugin changelog for any breaking changes between 2.0.3 and the target version; test in staging if possible

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

Fix this in Ulisting Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36880 — 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-2021-36880 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