# CVE-2021-47932: WordPress TheCartPress 1.5.3.6 Privilege Escalation Unauthenticated

> Unauthenticated attackers can create administrator accounts via crafted AJAX requests, gaining full administrative access to the WordPress site.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-r2pw-m85m-3mfq

## What is CVE-2021-47932?

CVE-2021-47932 is a critical vulnerability in TheCartPress, published on 10 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2021-47932?


## How do I fix CVE-2021-47932?

No fix has been published for CVE-2021-47932 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-47932 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47932 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47932 and fix it if it is affected.

What it is: CVE-2021-47932 is a critical vulnerability in TheCartPress, published on 10 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47932 exists.

Affected product: TheCartPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-47932/ (Markdown: https://insights.sbomify.com/CVE-2021-47932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-47932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-47932
- OSV: https://osv.dev/vulnerability/CVE-2021-47932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-47932/
Summaries are generated and may contain mistakes; the official description above is the record.