LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36876: WordPress uListing plugin <= 2.0.5 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities

Multiple Cross-Site Request Forgery (CSRF) vulnerabilities in WordPress uListing plugin (versions <= 2.0.5) as it lacks CSRF checks on plugin administration pages.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects WordPress sites running the StylemixThemes uListing plugin version 2.0.5 or earlier. The plugin’s administration pages lacked CSRF protections, so an attacker could trick a logged-in administrator into performing unintended actions. It is a medium-risk issue because user interaction is required and reported impact is limited to confidentiality and integrity.

Executive priority

Treat as a planned remediation item, not an emergency, unless uListing supports a business-critical public site with many administrators. Prioritize inventory and upgrade validation because WordPress plugin exposure is common and administrator compromise can affect site trust.

Technical view

CVE-2021-36876 is a CWE-352 CSRF weakness in uListing for WordPress through 2.0.5. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N. The flaw is tied to missing CSRF checks on plugin administration pages. Sources do not provide exploit details or a named fixed version.

Likely exposure

Exposure is limited to WordPress installations using the uListing plugin at version 2.0.5 or earlier. Sites without the plugin, or not using affected versions, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation would require user interaction, likely involving a logged-in site administrator being induced to trigger a forged administrative request.

Researcher notes

The provided evidence establishes affected product, version range, CWE, CVSS, and missing CSRF checks. It does not include endpoint names, exact administrative actions, proof-of-concept details, active exploitation, or a specific fixed version. Avoid assuming broader WordPress or StylemixThemes product impact.

Mitigation direction

  • Inventory WordPress sites for the uListing plugin and installed version.
  • Check WordPress.org, StylemixThemes, and Patchstack guidance for a vendor-confirmed fixed release.
  • Upgrade only to a vendor-confirmed non-affected version.
  • Temporarily disable uListing where exposure cannot be quickly validated.
  • Restrict administrator browsing and require reauthentication for sensitive admin workflows where possible.

Validation and detection

  • Confirm whether uListing is installed on each WordPress site.
  • Record plugin versions and flag any version at or below 2.0.5.
  • Review plugin administration pages for CSRF nonce or token enforcement.
  • Check security monitoring for suspicious administrator-initiated plugin changes.
  • Verify any remediation against vendor or Patchstack advisory information.
Prepared
Confidence
high
Sources
4

Public sources used

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-36876 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
5.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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

Source materials

Affected products

Products and packages named in the record

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

CWE details

CWE-352

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