dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-3861

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Prevent Direct Access – Protect WordPress Files plugin for WordPress is vulnerable to unauthorized access and modification of data| due to a misconfigured capability check on the 'pda_lite_custom_permission_check' function in versions 2.8.6 to 2.8.8.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to access and change the protection status of media.

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 Prevent Direct Access plugin for WordPress has a broken access control vulnerability in the pda_lite_custom_permission_check function. Versions 2.8.6 through 2.8.8.2 fail to properly validate user capabilities, allowing authenticated users with Contributor-level permissions to modify the protection status of media files that should be restricted.

MitigationUpdate to a patched version of the plugin when available, or implement additional access control checks around the affected function to verify users have appropriate permissions before allowing protection status changes.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Check the installed version of the Prevent Direct Access plugin
    In WordPress admin, go to Plugins > Installed Plugins and locate Prevent Direct Access (or PDA Lite). Note the version number displayed. Alternatively, check the plugin header in the main plugin file (typically /wp-content/plugins/prevent-direct-access-lite/ or similar path containing 'prevent-direct-access').
    Affected if The version number is 2.8.6, 2.8.7, 2.8.8, 2.8.8.1, or 2.8.8.2 (any version from 2.8.6 through 2.8.8.2).
  2. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the Prevent Direct Access plugin shows as Active.
    Affected if The plugin is active and the version falls within the affected range.
  3. Locate and inspect the pda_lite_custom_permission_check function
    Access the plugin files via FTP or file manager. Search for the function named pda_lite_custom_permission_check in PHP files within the plugin directory. Examine the function code to see if it performs capability checks (such as checking for 'edit_posts' or higher privileges) before allowing protection status changes.
    Affected if The function exists but lacks proper capability validation (e.g., does not check for 'edit_others_posts' or 'manage_options' before allowing media protection changes).
  4. Test Contributor role access to media protection features
    Using a test account with Contributor role, attempt to access media file protection settings. In WordPress, go to Media library, select a file, and check if protection options (such as preventing direct access, setting file visibility) are available or modifiable by this low-privileged user.
    Affected if A user with Contributor role can successfully modify the protection status of media files that should be restricted to higher-privileged users.

You are affected if the Prevent Direct Access plugin version is between 2.8.6 and 2.8.8.2 inclusive, the plugin is active, and users with Contributor-level permissions can modify media file protection settings.

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

Update to a patched version of the plugin when available, or implement additional access control checks around the affected function to verify users have appropriate permissions before allowing protection status changes.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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