# CVE-2026-122049: Campcodes Bitcoin Wallet System ForgotPasswordController.php random_int excessive authentication


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-8hhg-gmvm-688v

## What is CVE-2026-122049?

CVE-2026-122049 is a medium-severity vulnerability in Campcodes Bitcoin Wallet System, published on 4 Nov 2026. 

### Official description

A flaw has been found in Campcodes Bitcoin Wallet System 1.0. This affects the function random_int of the file core/app/Http/Controllers/Auth/ForgotPasswordController.php. This manipulation causes improper restriction of excessive authentication attempts. Remote exploitation of the attack is possible. The attack's complexity is rated as high. It is indicated that the exploitability is difficult. The exploit has been published and may be used.

Weakness: CWE-799 (Improper Control of Interaction Frequency), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-122049?


## How do I fix CVE-2026-122049?

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

## Is CVE-2026-122049 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-122049 and fix it if it is affected.

What it is: CVE-2026-122049 is a medium-severity vulnerability in Campcodes Bitcoin Wallet System, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122049 exists.

Affected product: Campcodes Bitcoin Wallet System. 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-2026-122049/ (Markdown: https://insights.sbomify.com/CVE-2026-122049/index.md)
```

## Sources

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

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