# CVE-2025-2413: OTP Bypass in Akinsoft's ProKuafor

> Attackers can bypass authentication in Akinsoft ProKuafor due to missing restrictions on excessive login attempts, potentially gaining unauthorized access.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-6j4r-889x-2cqf

## What is CVE-2025-2413?

CVE-2025-2413 is a high-severity authentication bypass vulnerability in Akinsoft ProKuafor, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Restriction of Excessive Authentication Attempts vulnerability in Akinsoft ProKuafor allows Authentication Bypass.

This issue affects ProKuafor: from s1.02.08 before v1.02.08.

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

## Which versions are affected by CVE-2025-2413?


## How do I fix CVE-2025-2413?

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

## Is CVE-2025-2413 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2413 and fix it if it is affected.

What it is: CVE-2025-2413 is a high-severity authentication bypass vulnerability in Akinsoft ProKuafor, published on 2 Sep 2025. 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-2025-2413 in the wild and no public exploit code.

Affected product: Akinsoft ProKuafor. 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-2025-2413/ (Markdown: https://insights.sbomify.com/CVE-2025-2413/index.md)
```

## Sources

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

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