# CVE-2024-6321: ScrollTo Bottom <= 1.1.1 - Cross-Site Request Forgery to Arbitrary File Upload

> Attackers can trick admins into uploading arbitrary files via CSRF, potentially leading to remote code execution on WordPress sites.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 9 Jul 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v3jv-5cgh-j56c

## What is CVE-2024-6321?

CVE-2024-6321 is a high-severity vulnerability in dwieeb ScrollTo Bottom, published on 9 Jul 2024. 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

The ScrollTo Bottom plugin for WordPress is vulnerable to Cross-Site Request Forgery to Arbitrary File Upload in versions up to, and including, 1.1.1. This is due to missing nonce validation and missing file type validation in the 'options_page' function. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

## Which versions are affected by CVE-2024-6321?


## How do I fix CVE-2024-6321?

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

## Is CVE-2024-6321 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6321 and fix it if it is affected.

What it is: CVE-2024-6321 is a high-severity vulnerability in dwieeb ScrollTo Bottom, published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-6321 in the wild and no public exploit code.

Affected product: dwieeb ScrollTo Bottom. 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-2024-6321/ (Markdown: https://insights.sbomify.com/CVE-2024-6321/index.md)
```

## Sources

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

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