dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-32679

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in Anssi Laitila Shared Files shared-files.This issue affects Shared Files: from n/a through <= 1.7.16.

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 · moderate confidence

A missing authorization vulnerability in the Shared Files WordPress plugin (versions <= 1.7.16) allows unauthenticated or unauthorized users to access functionality or data that should require proper permission checks. This authorization bypass could enable viewing, downloading, or manipulating files that should be restricted.

MitigationUpgrade to Shared Files version 1.7.17 or later which implements proper authorization checks. If immediate patching is not possible, restrict access at the server level (e.g., via .htaccess or firewall rules) to limit exposure.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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. Verify Shared Files plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Shared Files' in the list. Note the version number displayed below the plugin name.
    Affected if Plugin is present with version 1.7.16 or lower
  2. Check plugin version via file inspection
    Access the plugin main file via FTP or file manager at /wp-content/plugins/shared-files/readme.txt or /wp-content/plugins/shared-files/shared-files.php and locate the 'Version:' entry in the file header.
    Affected if Version shown is 1.7.16 or lower
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the Shared Files plugin shows as 'Active' under its status.
    Affected if Plugin is active and version is 1.7.16 or lower
  4. Test unauthenticated file access
    Attempt to access a file that should require authorization using a browser in incognito mode, for example: visit your-site.com/?sf_data=1&sf_download=1 or similar Shared Files endpoints without logging in.
    Affected if File downloads or content displays without requiring login or permission check
  5. Review server access logs
    Check your web server access logs (Apache/nginx) for requests to /?sf_ or /?shared_file= or similar Shared Files query parameters originating from unexpected IP addresses or unauthenticated sessions.
    Affected if Unauthenticated requests to Shared Files endpoints are logged and return successful HTTP 200 responses

Your environment is affected if Shared Files plugin version 1.7.16 or lower is installed and active, and the vulnerable file access functionality is exposed without proper authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Shared Files version 1.7.17 or later which implements proper authorization checks. If immediate patching is not possible, restrict access at the server level (e.g., via .htaccess or firewall rules) to limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32679 — 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-32679 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