dbcve.org
UlistingWordPress extension · Stylemixthemes

CVE-2021-36877

MEDIUM · 6.5 CVSS v3.1 Published 2021-09-27
Fix available
A fix is available. Upgrade to after 2.0.5 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in WordPress uListing plugin (versions <= 2.0.5) makes it possible for attackers to modify user roles.

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

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress uListing plugin (versions 2.0.5 and below) allows attackers to craft malicious requests that trick authenticated administrators into unintentionally modifying user role assignments. The plugin lacks proper anti-CSRF token validation on role modification actions, enabling privilege escalation via forged HTTP requests.

MitigationUpdate uListing plugin to version greater than 2.0.5 once available; alternatively, disable the plugin until a patched version is released. Implement CSRF nonces on all state-changing operations as a defense-in-depth measure.

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.5

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

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

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. Check if uListing plugin is installed
    Navigate to WordPress admin > Plugins, or inspect wp-content/plugins/ directory for 'ulisting' folder, or query database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'
    Affected if Plugin appears in active or installed plugins list
  2. Determine installed uListing version
    Check plugin header in wp-content/plugins/ulisting/readme.txt or ulisting.php for 'Version:' field, or view plugin details in WordPress admin Plugins page
    Affected if Version number is 2.0.5 or lower
  3. Verify role modification functionality exists
    Check if user role management features are accessible: navigate to uListing > User Roles or similar admin section, or inspect plugin files for role modification code paths (functions handling user role updates)
    Affected if Role modification interface is present and accessible to administrators
  4. Confirm lack of CSRF protection on role actions
    Inspect plugin PHP files (such as controller or ajax handlers) for nonce verification when handling role assignment actions; look for wp_verify_nonce or check_ajax_referer calls on role change endpoints
    Affected if No nonce verification found on role modification AJAX/actions or nonce checks are missing entirely

User is affected if uListing plugin version is 2.0.5 or lower AND role modification functionality is accessible to authenticated administrators AND the plugin lacks CSRF token validation on those actions.

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.5
Interim mitigation

Update uListing plugin to version greater than 2.0.5 once available; alternatively, disable the plugin until a patched version is released. Implement CSRF nonces on all state-changing operations as a defense-in-depth measure.

Recommended fix Moderate confidence

uListing version 2.0.6 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the uListing plugin in the list
  4. 4. Click the 'Update now' link if an update is available, or manually download the latest version from wordpress.org
  5. 5. Verify the update completes successfully
  6. 6. Test that user role management functionality in uListing continues to work correctly
  7. 7. Confirm the plugin version after update to ensure you are running a version newer than 2.0.5

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

Fix this in Ulisting Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.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-36877 — 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-36877 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