# CVE-2021-24647: Pie Register < 3.7.1.6 - Unauthenticated Arbitrary Login

> Unauthenticated attackers can log in as any user by knowing their ID or username due to a flaw in the social login implementation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-m4pp-cj4x-58f6

## What is CVE-2021-24647?

CVE-2021-24647 is a high-severity authentication bypass vulnerability in Unknown Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes, published on 8 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes WordPress plugin before 3.1.7.6 has a flaw in the social login implementation, allowing unauthenticated attacker to login as any user on the site by only knowing their user ID or username

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Genetechsolutions Pie Register.

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

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

## Is CVE-2021-24647 being exploited?

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

Public exploit code:

- CVE-2021-24647 Pie Register < 3.7.1.6 - Unauthenticated Arbitrary Login (github_poc): https://github.com/RandomRobbieBF/CVE-2021-24647
- Pie Register < 3.7.1.6 - Unauthenticated Arbitrary Login (nuclei): http/cves/2021/CVE-2021-24647.yaml

## Other vulnerabilities in Unknown Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes

- [CVE-2024-27957](https://insights.sbomify.com/CVE-2024-27957/): WordPress Pie Register plugin <= 3.8.3.1 - Unauthenticated Arbitrary File Upload vulnerability (critical 10.0)
- [CVE-2021-24731](https://insights.sbomify.com/CVE-2021-24731/): Pie Register < 3.7.1.6 - Unauthenticated SQL Injection (critical 9.8)
- [CVE-2019-15659](https://insights.sbomify.com/CVE-2019-15659/): SQL injection in n/a (critical 9.8)
- [CVE-2018-10969](https://insights.sbomify.com/CVE-2018-10969/): SQL injection in n/a (critical 9.8)
- [CVE-2022-4024](https://insights.sbomify.com/CVE-2022-4024/): Pie Register < 3.8.1.3 - Unauthenticated Arbitrary User Deletion (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24647 is a high-severity authentication bypass vulnerability in Unknown Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes, published on 8 Nov 2021. 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-24647 exists.

Affected product: Unknown Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes. 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-24647/ (Markdown: https://insights.sbomify.com/CVE-2021-24647/index.md)
```

## Sources

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

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