dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-6321

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ScrollTo Bottom WordPress plugin versions up to 1.1.1 lack nonce validation and file type validation in its options_page function. This allows unauthenticated attackers to craft CSRF attacks that force an authenticated administrator to unknowingly upload malicious files to the server, potentially achieving remote code execution.

MitigationUpdate the ScrollTo Bottom plugin to the latest patched version immediately. If no patch is available, deactivate and remove the plugin. Audit the wp-content/uploads directory for suspicious files and monitor for indicators of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ScrollTo Bottom plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'ScrollTo Bottom' in the plugin list. Note the version number displayed below the plugin name.
    Affected if The plugin is present in the installed plugins list with a version number of 1.1.1 or lower.
  2. Compare installed version against affected range
    Locate the plugin version number from the Plugins page or check the plugin's main PHP file (usually in wp-content/plugins/scrollto-bottom/ or similar naming) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 1.1.1 or any version lower than 1.1.1.
  3. Verify plugin directory exists
    Check the WordPress plugins directory on the server for a folder named 'scrollto-bottom', 'scroll-to-bottom', or similar variant containing the plugin files.
    Affected if The plugin directory exists in wp-content/plugins/.
  4. Inspect uploads directory for suspicious files
    Examine the wp-content/uploads/ directory (and subdirectories) for any recently uploaded PHP files, shell scripts, or unfamiliar file types that were not intentionally uploaded by legitimate administrators.
    Affected if Unexpected PHP files or suspicious executables are found in the uploads directory, especially with recent creation dates.
  5. Review plugin options for injected content
    Access the plugin's settings page (usually under Settings > ScrollTo Bottom or similar) and inspect any text/textarea fields for malicious JavaScript or PHP code that may have been injected via the options_page function.
    Affected if The plugin settings contain unfamiliar or malicious code that was not entered by the legitimate administrator.

A user is affected if the ScrollTo Bottom plugin is installed with version 1.1.1 or lower, making the insecure options_page function exploitable for unauthorized file uploads via CSRF.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the ScrollTo Bottom plugin to the latest patched version immediately. If no patch is available, deactivate and remove the plugin. Audit the wp-content/uploads directory for suspicious files and monitor for indicators of compromise.

Recommended fix High confidence

Version 1.1.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'ScrollTo Bottom' plugin
  4. Check if the current version is 1.1.1 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the updated plugin zip file from wordpress.org/plugins/scrollto-bottom
  7. After updating, verify the new version number reflects the fix (version 1.1.2 or later)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6321 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data