dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-40779

HIGH · 7.7 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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
Contributor Arbitrary File Deletion in Link Library <= 7.8.8 versions.

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

The Link Library WordPress plugin (versions 7.8.8 and below) has a contributor-level arbitrary file deletion vulnerability. Users with contributor privileges can delete arbitrary files on the server due to insufficient access controls on a file deletion function, likely through a missing capability check or unsafe use of filesystem operations.

MitigationUpdate Link Library plugin to the latest patched version. If no patch is available, restrict or revoke contributor-level user permissions, or temporarily disable the plugin until a fix is available.

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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. Verify Link Library plugin is installed
    Log in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Link Library' in the plugin list.
    Affected if Link Library plugin appears in the installed plugins list
  2. Determine installed version of Link Library
    In the Plugins list, locate Link Library and note the version number displayed below the plugin name. Compare this to the affected range: 7.8.8 and below.
    Affected if Version number is 7.8.8 or lower
  3. Check for contributor-level user accounts
    Navigate to Users > All Users in WordPress admin, and look for any users with the 'Contributor' role assigned.
    Affected if At least one user account with Contributor role exists on the site
  4. Verify file deletion capability is accessible
    Review the Link Library plugin files (specifically PHP files handling deletion operations) for functions that process file paths without capability checks. Use code search for functions like unlink or wp_delete_file called without current_user_can checks.
    Affected if Deletion functions exist in the plugin without proper capability verification (requires code review or penetration testing to confirm)

You are affected if the Link Library plugin is installed at version 7.8.8 or below AND your site has at least one user with Contributor role, because such users can exploit the unprotected file deletion function.

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 Link Library plugin to the latest patched version. If no patch is available, restrict or revoke contributor-level user permissions, or temporarily disable the plugin until a fix is available.

Recommended fix Moderate confidence

Latest version of Link Library (7.8.9 or higher)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Link Library' plugin
  4. 4. Check the current installed version number
  5. 5. If the installed version is 7.8.8 or lower, click 'Update Now' to update to the latest version
  6. 6. Alternatively, download the latest version from the WordPress plugin repository and upload manually

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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