# CVE-2023-6272: Theme My Login 2FA < 1.2 - Lack of Rate Limiting

> Attackers can bypass two-factor authentication by brute-forcing six-digit codes due to missing rate limiting in the Theme My Login 2FA plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 18 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-m6gh-58ph-rm3q

## What is CVE-2023-6272?

CVE-2023-6272 is a critical vulnerability in Unknown tml-2fa, published on 18 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Theme My Login 2FA WordPress plugin before 1.2 does not rate limit 2FA validation attempts, which may allow an attacker to brute-force all possibilities, which shouldn't be too long, as the 2FA codes are 6 digits.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2023-6272?

It affects 1 product.


Products: Thememylogin 2fa.

## How do I fix CVE-2023-6272?

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

## Is CVE-2023-6272 being exploited?

There is no known exploitation of CVE-2023-6272 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6272 and fix it if it is affected.

What it is: CVE-2023-6272 is a critical vulnerability in Unknown tml-2fa, published on 18 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6272 in the wild and no public exploit code.

Affected product: Unknown tml-2fa. 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-2023-6272/ (Markdown: https://insights.sbomify.com/CVE-2023-6272/index.md)
```

## Sources

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

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