LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36877: WordPress uListing plugin <= 2.0.5 - Modify User Roles via Cross-Site Request Forgery (CSRF) vulnerability

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

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This WordPress uListing plugin issue can let an attacker trick a logged-in user into changing user roles. It affects uListing versions up to and including 2.0.5. The business risk is unauthorized privilege or account role changes, not direct data theft or outage based on the supplied CVSS data.

Executive priority

Treat as a moderate-priority WordPress plugin issue. It is not reported as actively exploited in the supplied sources, but it can affect account integrity if privileged users are tricked. Remediate affected internet-facing WordPress sites during the next normal patch window, sooner for high-value sites.

Technical view

CVE-2021-36877 is a CWE-352 CSRF vulnerability in StylemixThemes uListing for WordPress <= 2.0.5. CVSS 3.1 is 4.3, with network reachability, low attack complexity, no attacker privileges, required user interaction, and low integrity impact. The supplied sources do not include exploit mechanics or complete remediation details.

Likely exposure

Exposure is limited to WordPress sites running the uListing plugin at version 2.0.5 or earlier. Sites with active administrative sessions and users who manage listings or accounts are the most relevant targets. The source bundle does not identify other affected products.

Exploitation context

The supplied bundle does not show active exploitation, and KEV is false. Exploitation requires user interaction, consistent with CSRF: a targeted logged-in user must be induced to trigger an unintended role-changing action. Public detail is limited.

Researcher notes

The key uncertainty is remediation detail: the bundle states affected versions <= 2.0.5 but does not provide a confirmed fixed version or patch note text. Validation should stay focused on installed plugin version, role-change evidence, and vendor guidance rather than inferred fixes.

Mitigation direction

  • Inventory WordPress sites for the uListing plugin and record installed versions.
  • Prioritize sites running uListing 2.0.5 or earlier for remediation review.
  • Check WordPress.org, StylemixThemes, and Patchstack guidance for the fixed version or vendor workaround.
  • Restrict administrative access and reduce persistent admin sessions until remediated.
  • Review recent account and role changes for unexpected modifications.

Validation and detection

  • Confirm whether uListing is installed and enabled on each WordPress site.
  • Verify the plugin version is greater than the affected range, if vendor guidance confirms a fixed release.
  • Review WordPress user role audit logs or backups for unauthorized role changes.
  • Check whether privileged users were recently targeted with suspicious links or messages.
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.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-36877 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-36877Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.