dbcve.org
UlistingWordPress extension · Stylemixthemes

CVE-2021-36874

HIGH · 8.8 CVSS v3.1 Published 2021-09-27
Fix available
A fix is available. Upgrade to after 2.0.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Authenticated Insecure Direct Object References (IDOR) vulnerability in WordPress uListing plugin (versions <= 2.0.5).

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

Authenticated IDOR vulnerability in WordPress uListing plugin versions up to 2.0.5 allows logged-in users to access or modify data objects they should not have authorization to access by manipulating object references in requests.

MitigationUpgrade uListing plugin to version 2.0.6 or later; alternatively, implement proper authorization validation checks on all data access endpoints to verify user permissions before returning or modifying objects.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm uListing plugin is installed
    Log into WordPress admin dashboard, go to Plugins section, and verify that the uListing plugin by Stylemixthemes is present and activated
    Affected if uListing plugin is installed and active in WordPress
  2. Check installed uListing version
    In WordPress admin under Plugins > uListing, view the plugin details to locate the version number
    Affected if Version is 2.0.5 or earlier (versions 2.0.6 and later contain the fix)
  3. Determine if authentication is required for uListing endpoints
    Use a browser or HTTP tool to identify which uListing URLs accept requests and whether they require a logged-in session
    Affected if uListing data endpoints are accessible to any authenticated WordPress user (subscriber, contributor, author, editor, or administrator)
  4. Verify lack of ownership validation in requests
    As a logged-in user with minimal privileges, attempt to access or modify a uListing data object by changing the object ID parameter in the request to reference an object owned by another user
    Affected if The request succeeds and returns or modifies data that the user does not own

User is affected if uListing plugin version 2.0.5 or lower is installed and any logged-in user can access data objects they should not be authorized to see or modify.

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

Upgrade uListing plugin to version 2.0.6 or later; alternatively, implement proper authorization validation checks on all data access endpoints to verify user permissions before returning or modifying objects.

Recommended fix Moderate confidence

uListing version 2.0.6 or later (latest stable release)

  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. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, manually download the updated uListing plugin from the official WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is functioning correctly by testing listing creation, editing, and user role permissions.

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

Fix this in Ulisting Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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