LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36874: WordPress uListing plugin <= 2.0.5 - Authenticated Insecure Direct Object References (IDOR) vulnerability

Authenticated Insecure Direct Object References (IDOR) vulnerability in WordPress uListing plugin (versions <= 2.0.5).

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using the uListing plugin version 2.0.5 or earlier. A logged-in attacker could manipulate objects they should not control, creating high integrity risk and some availability risk. The source bundle does not show data disclosure impact or confirmed active exploitation.

Executive priority

Prioritize remediation on internet-facing WordPress sites, especially where customers, agents, or contributors can log in. This is not marked as actively exploited in the provided sources, but the low attack complexity and high integrity impact justify near-term action.

Technical view

CVE-2021-36874 is an authenticated IDOR in StylemixThemes uListing for WordPress, affecting versions <= 2.0.5. CVSS 3.1 is 7.1: network reachable, low complexity, low privileges, no user interaction, unchanged scope, high integrity impact, low availability impact, and no confidentiality impact.

Likely exposure

Exposure is limited to WordPress sites with uListing version 2.0.5 or earlier, especially sites allowing untrusted or low-privilege user accounts. Sites without the plugin, or with versions outside the affected range, are not indicated as affected by the supplied sources.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of in-the-wild exploitation. The vulnerability still has practical risk because it is network reachable, low complexity, and only requires authentication. Treat public WordPress sites with user registration or broad contributor access as higher priority.

Researcher notes

The bundle does not include endpoint details, proof of concept, exact authorization bypass mechanics, or a named fixed version. Analysis should stay focused on authenticated IDOR exposure in uListing <= 2.0.5 and validation through version inventory, role review, and vendor guidance.

Mitigation direction

  • Inventory all WordPress sites for the uListing plugin and installed version.
  • Update or remove uListing installations at or below version 2.0.5 per vendor guidance.
  • Restrict WordPress account creation and plugin-accessible roles until remediation is complete.
  • Review vendor, WordPress.org, and Patchstack guidance for confirmed fixed versions.
  • Back up affected sites before plugin updates or removal.

Validation and detection

  • Confirm whether each WordPress site has uListing installed.
  • Verify no production site reports uListing version 2.0.5 or earlier.
  • Review user roles with access to uListing-related functionality.
  • Check application logs for suspicious authenticated object changes.
  • Document remediation status for each affected WordPress instance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-36874 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2021-36874Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
StylemixThemesuListing (WordPress plugin)<= 2.0.5Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.