# CVE-2010-4266: It was found in vanilla forums before 2.0.10 a potential linkbait vulnerability in dispatcher.


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Jun 2021
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wc79-hvvx-2qpw

## What is CVE-2010-4266?

CVE-2010-4266 is a medium-severity vulnerability in vanilla forums, published on 22 Jun 2021. 

### Official description

It was found in vanilla forums before 2.0.10 a potential linkbait vulnerability in dispatcher.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2010-4266?

It affects 1 product.


Products: Vanillaforums Vanilla Forums.

## How do I fix CVE-2010-4266?

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

## Is CVE-2010-4266 being exploited?

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

## Other vulnerabilities in vanilla forums

- [CVE-2017-1000432](https://insights.sbomify.com/CVE-2017-1000432/): Cross-site request forgery in n/a (high 8.0)
- [CVE-2010-4264](https://insights.sbomify.com/CVE-2010-4264/): Cross-site scripting in vanilla forums (medium 6.1)
- [CVE-2019-8279](https://insights.sbomify.com/CVE-2019-8279/): Cross-site scripting in Vanilla Forums (medium 5.4)
- [CVE-2018-15833](https://insights.sbomify.com/CVE-2018-15833/): Business logic in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4266 and fix it if it is affected.

What it is: CVE-2010-4266 is a medium-severity vulnerability in vanilla forums, published on 22 Jun 2021. 
Exploitation: There is no known exploitation of CVE-2010-4266 in the wild and no public exploit code.

Affected product: vanilla forums. 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-2010-4266/ (Markdown: https://insights.sbomify.com/CVE-2010-4266/index.md)
```

## Sources

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

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