# CVE-2022-50910: Beehive Forum - Account Takeover

> Attackers can hijack user accounts by injecting malicious host headers into password reset requests to intercept reset tokens.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-cm5v-3gc5-6w7v

## What is CVE-2022-50910?

CVE-2022-50910 is a high-severity vulnerability in Beehive Forum, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Beehive Forum 1.5.2 contains a host header injection vulnerability in the forgot password functionality that allows attackers to manipulate password reset requests. Attackers can inject a malicious host header to intercept password reset tokens and change victim account passwords without direct authentication.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2022-50910?

It affects 1 product.


Products: Beehiveforum Beehive Forum.

## How do I fix CVE-2022-50910?

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

## Is CVE-2022-50910 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50910 and fix it if it is affected.

What it is: CVE-2022-50910 is a high-severity vulnerability in Beehive Forum, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50910 exists.

Affected product: Beehive Forum. 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-2022-50910/ (Markdown: https://insights.sbomify.com/CVE-2022-50910/index.md)
```

## Sources

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

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