dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2024-8988

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-14
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
The PeepSo Core: File Uploads plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.4.6.0 via the file_download REST API endpoint due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to download files uploaded by others users and expose potentially sensitive information.

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 PeepSo Core: File Uploads plugin for WordPress contains an Insecure Direct Object Reference (IDOR) vulnerability in the file_download REST API endpoint. The endpoint fails to validate a user-controlled key that references the file being requested, allowing unauthenticated attackers to access files uploaded by other users by manipulating this key parameter.

MitigationUpdate the plugin to version 6.4.6.1 or later where proper authorization validation has been implemented on the file_download REST API endpoint to verify the requesting user has permission to access the requested file.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify if PeepSo Core: File Uploads plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PeepSo Core: File Uploads' or check the plugin files in wp-content/plugins/ directory for the peepso-file-upload folder
    Affected if The plugin is not installed or not present in the environment
  2. Determine the installed version of the PeepSo File Uploads plugin
    In WordPress admin, go to Plugins > Installed Plugins, find PeepSo Core: File Uploads, and note the version number displayed; alternatively, check the main plugin file header in peepso-file-upload/peepso-file-upload.php for the Version field
    Affected if The installed version is lower than 6.4.6.1 (the patched version)
  3. Verify the file_download REST API endpoint is accessible
    Send a GET request to the REST API endpoint (typically /wp-json/peepso-file-upload/v1/file_download) with a manipulated key parameter, such as ?key=[any numeric value] to see if the endpoint responds without proper authorization checks
    Affected if The endpoint returns file data or error messages that reveal file information without requiring authentication or ownership validation
  4. Check if file upload functionality is enabled in the plugin settings
    In WordPress admin, navigate to PeepSo > Configuration > File Uploads (or similar settings path) and check if file upload features are turned on
    Affected if File upload features are enabled and the vulnerable REST API endpoint is exposed

You are affected if the PeepSo Core: File Uploads plugin version is below 6.4.6.1 and the file_download REST API endpoint is accessible without proper authorization validation on the key parameter.

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 plugin to version 6.4.6.1 or later where proper authorization validation has been implemented on the file_download REST API endpoint to verify the requesting user has permission to access the requested file.

Recommended fix Moderate confidence

Version greater than 6.4.6.0 (check WordPress plugin repository or PeepSo for latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'PeepSo Core: File Uploads' plugin
  4. 4. Check the current installed version (should be 6.4.6.0 or earlier)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update completed successfully
  7. 7. Test the file_download REST API endpoint to confirm the vulnerability is patched

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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