LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4343: uListing <= 1.6.6 - Unauthenticated Arbitrary Account Creation

The Unauthenticated Account Creation plugin for WordPress is vulnerable to Unauthenticated Account Creation in versions up to, and including, 1.6.6. This is due to the stm_listing_register AJAX action function being accessible and taking roles unprotected. This makes it possible for unauthenticated attackers to create accounts, even those with administrator privileges.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A vulnerable uListing WordPress plugin version could let an unauthenticated visitor create a new site account with administrator privileges. For affected public WordPress sites, this can become full website takeover, content tampering, data exposure, and service disruption.

Executive priority

Prioritize within the next maintenance window or faster for public sites. The business risk is direct administrative takeover of affected WordPress properties, with potential customer trust, data, and operational impacts.

Technical view

CVE-2021-4343 is a missing authorization issue in uListing up to and including 1.6.6. The stm_listing_register AJAX action was accessible without proper protection and accepted attacker-controlled role values, allowing unauthenticated account creation including administrator accounts.

Likely exposure

Exposure is most likely on internet-facing WordPress sites running the uListing directory listings plugin at versions up to 1.6.6. Sites without the plugin, or running a fixed version, are not shown as affected by the provided sources.

Exploitation context

The sources describe unauthenticated remote account creation with administrator privileges, but the bundle does not show CISA KEV listing or other cited evidence of active exploitation. Treat exploitable affected sites as urgent because attack complexity and privileges required are low.

Researcher notes

The issue maps to CWE-862 and centers on missing authorization around stm_listing_register plus unprotected role handling. Evidence supports critical severity, but the provided affected-version metadata is limited, so confirm deployment details against vendor or WordPress plugin records.

Mitigation direction

  • Inventory WordPress sites for the uListing plugin and record installed versions.
  • Update uListing to a vendor-fixed release if still deployed.
  • Disable or remove the plugin where a fixed release cannot be confirmed.
  • Review WordPress administrator accounts for unauthorized additions.
  • Preserve relevant logs before cleanup for incident review.

Validation and detection

  • Confirm whether uListing is installed on each WordPress site.
  • Verify installed versions are not up to and including 1.6.6.
  • Check user records for unexpected administrator accounts.
  • Review web and application logs for suspicious registration activity.
  • Confirm the vulnerable registration path no longer accepts untrusted role assignment.
Prepared
Confidence
high
Sources
5

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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-4343 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
4Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-4343Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
stylemixDirectory Listings WordPress plugin – uListing0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.