# CVE-2024-54294: WordPress Firebase OTP Authentication plugin <= 1.0.1 - Account Takeover vulnerability

> Attackers can bypass authentication in the Firebase OTP Authentication plugin to take over user accounts.

- **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:** 13 Dec 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-xjg4-367c-227h

## What is CVE-2024-54294?

CVE-2024-54294 is a critical authentication bypass vulnerability in Appgenix Infotech Firebase OTP Authentication, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Appgenix Infotech Firebase OTP Authentication authentication-via-otp-using-firebase allows Authentication Bypass.This issue affects Firebase OTP Authentication: from n/a through <= 1.0.1.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2024-54294?


## How do I fix CVE-2024-54294?

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

## Is CVE-2024-54294 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-54294 and fix it if it is affected.

What it is: CVE-2024-54294 is a critical authentication bypass vulnerability in Appgenix Infotech Firebase OTP Authentication, published on 13 Dec 2024. 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-2024-54294 in the wild and no public exploit code.

Affected product: Appgenix Infotech Firebase OTP Authentication. 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-2024-54294/ (Markdown: https://insights.sbomify.com/CVE-2024-54294/index.md)
```

## Sources

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

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