Missing AuthorizationWeakness · CWE-862

CVE-2021-47932

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
WordPress TheCartPress 1.5.3.6 contains an unauthenticated privilege escalation vulnerability that allows attackers to create administrator accounts by submitting crafted requests to the AJAX handler. Attackers can send POST requests to the tcp_register_and_login_ajax action with tcp_role set to administrator to gain full administrative access without authentication.

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

The TheCartPress WordPress plugin versions 1.5.3.6 and below contains an unauthenticated privilege escalation vulnerability in its AJAX handler. Attackers can send POST requests to the tcp_register_and_login_ajax action with the tcp_role parameter set to 'administrator' to create a new administrator account without any authentication, gaining full administrative access to the WordPress site.

MitigationImmediately update TheCartPress to the latest patched version or remove the plugin if no patch is available. Audit the WordPress installation for unauthorized administrator accounts created by attackers and remove them. Consider a full compromise assessment given the critical severity and complete administrative access gained.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify TheCartPress plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for TheCartPress in the list of installed plugins
    Affected if TheCartPress appears in the installed plugins list
  2. Check installed version of TheCartPress
    In the Plugins list, look at the version displayed beneath TheCartPress or check the plugin's main PHP file for the version constant
    Affected if The version listed is 1.5.3.6 or lower
  3. Inspect the tcp_register_and_login_ajax AJAX endpoint
    Check plugin source code for the tcp_register_and_login_ajax action handler and verify if the tcp_role parameter is validated before creating the user
    Affected if The code accepts the tcp_role parameter without proper authorization validation and allows setting it to 'administrator'
  4. Review user accounts for unauthorized administrators
    Go to WordPress Users panel and examine all accounts with Administrator role, focusing on any created recently or with unfamiliar email addresses
    Affected if There are administrator accounts that were not created by legitimate site administrators
  5. Check server access logs for POST requests to tcp_register_and_login_ajax
    Search HTTP access logs for POST requests containing 'tcp_register_and_login_ajax' and inspect for suspicious payloads with tcp_role=administrator
    Affected if Such requests exist from unknown IP addresses, especially in bulk or with unusual timing

You are affected if TheCartPress plugin version 1.5.3.6 or below is installed and the tcp_register_and_login_ajax endpoint is exposed, or if unauthorized administrator accounts exist on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update TheCartPress to the latest patched version or remove the plugin if no patch is available. Audit the WordPress installation for unauthorized administrator accounts created by attackers and remove them. Consider a full compromise assessment given the critical severity and complete administrative access gained.

Recommended fix Moderate confidence

Latest available version of TheCartPress from wordpress.org (check plugin repository for post-1.5.3.6 release)

  1. 1. Check the current version of TheCartPress plugin installed on your WordPress site.
  2. 2. If the installed version is 1.5.3.6 or earlier, navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate TheCartPress in the plugin list and check for available updates.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. After updating, verify the fix by attempting a test registration with tcp_role parameter to confirm the vulnerability is patched.
  6. 6. If no update is available from the WordPress plugin repository, consider: (a) contacting the plugin developer directly for a patched version, (b) disabling the plugin if not essential, or (c) implementing a web application firewall (WAF) rule to block requests with the tcp_role parameter.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-47932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-47932 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