Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-18855 – Unauthenticated Arbitrary File Deletion (potential RCE) – Link Library WordPress Pl

Be the first to know when new zero-days emerge:

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_fields function does not properly validate/sanitize the link_url parameter 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/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge