CVE-2021-47932
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 · uneditedWordPress 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 confidenceThe 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.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify TheCartPress plugin is installedNavigate to WordPress admin dashboard > Plugins and look for TheCartPress in the list of installed pluginsAffected if TheCartPress appears in the installed plugins list
-
Check installed version of TheCartPressIn the Plugins list, look at the version displayed beneath TheCartPress or check the plugin's main PHP file for the version constantAffected if The version listed is 1.5.3.6 or lower
-
Inspect the tcp_register_and_login_ajax AJAX endpointCheck plugin source code for the tcp_register_and_login_ajax action handler and verify if the tcp_role parameter is validated before creating the userAffected if The code accepts the tcp_role parameter without proper authorization validation and allows setting it to 'administrator'
-
Review user accounts for unauthorized administratorsGo to WordPress Users panel and examine all accounts with Administrator role, focusing on any created recently or with unfamiliar email addressesAffected if There are administrator accounts that were not created by legitimate site administrators
-
Check server access logs for POST requests to tcp_register_and_login_ajaxSearch HTTP access logs for POST requests containing 'tcp_register_and_login_ajax' and inspect for suspicious payloads with tcp_role=administratorAffected 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.
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 · scopedImmediately 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.
Latest available version of TheCartPress from wordpress.org (check plugin repository for post-1.5.3.6 release)
- 1. Check the current version of TheCartPress plugin installed on your WordPress site.
- 2. If the installed version is 1.5.3.6 or earlier, navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
- 3. Locate TheCartPress in the plugin list and check for available updates.
- 4. If an update is available, click 'Update Now' to install the latest version.
- 5. After updating, verify the fix by attempting a test registration with tcp_role parameter to confirm the vulnerability is patched.
- 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.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-47932 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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