# CVE-2017-1000432: Cross-site request forgery in n/a

> An attacker can trick an admin into deleting forum topics and comments via a cross-site request forgery attack.

- **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7vfx-jfc7-pxph

## What is CVE-2017-1000432?

CVE-2017-1000432 is a high-severity vulnerability in n/a, published on 2 Jan 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vanilla Forums below 2.1.5 are affected by CSRF leading to Deleting topics and comments from forums Admin access

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-1000432?

It affects 1 product.


Products: Vanillaforums Vanilla Forums.

## How do I fix CVE-2017-1000432?

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

## Is CVE-2017-1000432 being exploited?

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

Public exploit code:

- Vanilla < 2.1.5 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-4264](https://insights.sbomify.com/CVE-2010-4264/): Cross-site scripting in vanilla forums (medium 6.1)
- [CVE-2010-4266](https://insights.sbomify.com/CVE-2010-4266/): It was found in vanilla forums before 2.0.10 a potential linkbait vulnerability in dispatcher. (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-2017-1000432 and fix it if it is affected.

What it is: CVE-2017-1000432 is a high-severity vulnerability in n/a, published on 2 Jan 2018. Any signed-in user can exploit it over the network, 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-2017-1000432 exists.

Affected product: n/a. 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-2017-1000432/ (Markdown: https://insights.sbomify.com/CVE-2017-1000432/index.md)
```

## Sources

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

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