Summary
CVE-2026-18855 is a critical arbitrary file deletion vulnerability in the Link Library WordPress plugin, caused by insufficient path validation in the ll_delete_link_fields function. An attacker can supply a crafted link_url value to delete arbitrary files on the affected server, which can lead to remote code execution under certain server configurations. The flaw carries a CVSS v3.1 base score of 9.1 (Critical).
Technical details
- Root cause: the
ll_delete_link_fieldsfunction does not properly validate/sanitize thelink_urlparameter before using it in a file deletion operation, allowing path traversal outside the intended directory. - Trigger conditions: exploitation requires the site administrator to have enabled the plugin’s "Delete local file on link deletion" option; the attacker submits a malicious link entry (e.g., via the front-end link submission form) and the entry is then permanently deleted, triggering deletion of an attacker-chosen file.
- Attack vector: network — no authentication is required to submit the malicious link data (AV:N, PR:N, UI:N per the CVSS vector).
- Impact: full confidentiality is unaffected, but integrity and availability are severely impacted (deletion of arbitrary server files, e.g.,
wp-config.php), which can result in site takeover or remote code execution depending on which files are deleted and how the server responds.
Affected software
- Link Library WordPress plugin (vendor: jackdewey) — all versions from the earliest release through 7.9.4, inclusive.
Severity
- CVSS v3.1 Base Score: 9.1 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Mitigation and recommended actions
- Immediate: upgrade Link Library to version 7.9.5 or later, where the vulnerable file deletion logic has been corrected.
- If patching is not immediately possible: disable the "Delete local file on link deletion" option in the plugin settings to prevent the deletion trigger, and disable or restrict the front-end link submission form until the plugin is updated.
- Review server file integrity and WordPress core/config files for signs of unauthorized deletion following any suspected exploitation attempt.
How IONIX identifies potentially affected assets
IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
/wp-content/plugins/link-library/

