HomeWordPress vulnerabilitiesLink Library
Link Library vulnerabilities
Link Library has 21 known vulnerabilities in this database. The most recent published record is dated 18 Nov 2026.
- Known vulnerabilities
- 21
- Active installs
- 10,000+
- Latest version
- 7.10.1
- Last updated
- 1 Nov 2026
- Most recent
- 18 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-120049 | Medium 5.4 | Up to 7.10.0 | Fixed in a later version (latest 7.10.1) | 4 d ago |
| Cross-site scripting (XSS) CVE-2026-116537 | High 7.2 | Up to 7.10.0 | Fixed in a later version (latest 7.10.1) | 7 Nov 2026 |
| Broken access control CVE-2026-78395 | Medium 5.3 | Before 7.10.0 | Fixed in 7.10.0 | 29 Oct 2026 |
| Sensitive data exposure CVE-2026-78396 | Medium 5.3 | Before 7.10.0 | Fixed in 7.10.0 | 29 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-78392 | Medium 6.8 | Before 7.9.6 | Fixed in 7.9.6 | 22 Oct 2026 |
| SQL injection CVE-2026-15090 | High 7.5 | Up to 7.9.2 | Fixed in a later version (latest 7.10.1) | 15 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-78393 | Medium 6.1 | Before 7.9.6 | Fixed in 7.9.6 | 25 Sep 2026 |
| Path traversal CVE-2026-78394 | Medium 4.1 | Before 7.9.6 | Fixed in 7.9.6 | 25 Sep 2026 |
| Server-side request forgery (SSRF) CVE-2026-78397 | Medium 4.0 | Up to 7.9.5 | Fixed in a later version (latest 7.10.1) | 25 Sep 2026 |
| Remote code execution CVE-2026-18855 | Critical 9.1 | Up to 7.9.4 | Fixed in a later version (latest 7.10.1) | 15 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-16535 | Medium 6.1 | Before 7.9.4 | Fixed in 7.9.4 | 8 Aug 2026 |
| SQL injection CVE-2026-16532 | Critical 9.1 | Before 7.9.3 | Fixed in 7.9.3 | 3 Aug 2026 |
| Cross-site scripting (XSS) CVE-2025-2889 | Medium 6.4 | Up to 7.7.3 | Fixed in a later version (latest 7.10.1) | 5 Apr 2025 |
| Cross-site scripting (XSS) CVE-2024-13404 | Medium 6.1 | Before 7.7.3 | Fixed in 7.7.3 | 21 Jan 2025 |
| Cross-site scripting (XSS) CVE-2024-4281 | Medium 6.4 | Before 7.7 | Fixed in 7.7 | 8 May 2024 |
| Cross-site scripting (XSS) CVE-2024-2325 | Medium 6.1 | Before 7.6.7 | Fixed in 7.6.7 | 9 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-1559 | Medium 6.5 | Before 7.6.1 | Fixed in 7.6.1 | 20 Feb 2024 |
| Cross-site scripting (XSS) CVE-2022-4199 | Medium 4.8 | Before 7.4.1 | Fixed in 7.4.1 | 16 Jan 2023 |
| Cross-site scripting (XSS) CVE-2021-25091 | Medium 6.1 | Before 7.2.9 | Fixed in 7.2.9 | 1 Feb 2022 |
| Cross-site request forgery (CSRF) CVE-2021-25092 | Medium 6.5 | Before 7.2.8 | Fixed in 7.2.8 | 1 Feb 2022 |
| Broken access control CVE-2021-25093 | High 7.5 | Before 7.2.8 | Fixed in 7.2.8 | 1 Feb 2022 |
Read the published descriptions
- CVE-2026-120049, 18 Nov 2026
- The Link Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'linkfile[name]' parameter in all versions up to, and including, 7.10.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have enabled the "Link File" option within the plugin's settings, which activates the vulnerable file upload field on the public add-link form. CVE record
- CVE-2026-116537, 7 Nov 2026
- The Link Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'link_description' parameter in all versions up to, and including, 7.10.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This exploit requires the site administrator to have enabled the non-default 'Convert [] to <> in Link Description and Notes' (use_html_tags) setting; when this option is off, the bracket-to-angle-bracket conversion never runs and the payload is never reconstructed into executable HTML. CVE record
- CVE-2026-78395, 29 Oct 2026
- The Link Library WordPress plugin before 7.10.0 does not re-check the selected library's own login requirement when processing its front-end link submission, allowing unauthenticated users to submit links to a library configured to require login by reusing a form token obtained from another library that does not. CVE record
- CVE-2026-78396, 29 Oct 2026
- The Link Library WordPress plugin before 7.10.0 does not verify that a requested link belongs to the settings set whose display template is used to render it, allowing unauthenticated users to disclose the telephone number, e-mail address and submitter name stored with links that the settings set is configured not to display. CVE record
- CVE-2026-78392, 22 Oct 2026
- The Link Library WordPress plugin before 7.9.6 does not sanitise and escape a link field before outputting it inside an attribute of a link preview, allowing users with the Contributor role and above to perform Stored Cross-Site Scripting attacks. The preview is generated without authentication and without checking whether the link has been published, so an unapproved submission is enough to reach any visitor who opens it. CVE record
- CVE-2026-15090, 15 Oct 2026
- The Link Library plugin for WordPress is vulnerable to time-based SQL Injection via the 'link_url' parameter in all versions up to, and including, 7.9.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-78393, 25 Sep 2026
- The Link Library WordPress plugin before 7.9.6 does not properly escape some parameters before outputting them in the addresses of links it generates on its front-end directory pages, leading to Reflected Cross-Site Scripting which could be used against any visitor, including logged-in administrators. CVE record
- CVE-2026-78394, 25 Sep 2026
- The Link Library WordPress plugin before 7.9.6 does not sanitize a user-supplied destination folder before writing a generated image to disk, allowing users with the Contributor role and above to create directories and write or overwrite image files anywhere the web server can write, including outside the site's document root. The written file name is always numeric with a fixed image extension, so executable code cannot be planted this way. CVE record
- CVE-2026-78397, 25 Sep 2026
- The Link Library WordPress plugin before 7.9.6 does not validate the destination of a user-supplied URL before falling back to an unprotected fetch when its safe request is rejected, allowing unauthenticated visitors to make the site issue requests to hosts on its internal network and to learn from the response whether an internal service answered. Versions below 7.8.8 are covered by CVE-2025-68600; this entry covers 7.8.8 through 7.9.5, where that fix was incomplete. Exploitation requires the site owner to have published the Link Library WordPress plugin before 7.9.6's public link submission form with reciprocal-link validation enabled. CVE record
- CVE-2026-18855, 15 Aug 2026
- The Link Library plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the ll_delete_link_fields function in all versions up to, and including, 7.9.4 This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Exploitation requires the administrator to have enabled the 'Delete local file on link deletion' plugin option (disabled by default) and to subsequently permanently delete the attacker-submitted link, which is a routine moderation action. CVE record
- CVE-2026-16535, 8 Aug 2026
- The Link Library WordPress plugin before 7.9.4 does not sanitise and escape a parameter before reflecting it back in a response, allowing unauthenticated attackers to perform Reflected Cross-Site Scripting attacks against users who can be tricked into performing an action. CVE record
- CVE-2026-16532, 3 Aug 2026
- The Link Library WordPress plugin before 7.9.3 does not properly sanitise and escape a user-supplied value before using it in a SQL query, allowing unauthenticated users to perform SQL injection attacks. CVE record
- CVE-2025-2889, 5 Apr 2025
- The Link Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Link Additional Parameters in all versions up to, and including, 7.7.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-13404, 21 Jan 2025
- The Link Library plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'searchll' parameter in all versions up to, and including, 7.7.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2024-4281, 8 May 2024
- The Link Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'link-library' shortcode in all versions up to, and including, 7.6.11 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-2325, 9 Apr 2024
- The Link Library plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the searchll parameter in all versions up to, and including, 7.6.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2024-1559, 20 Feb 2024
- The Link Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'll_reciprocal' parameter in all versions up to, and including, 7.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2022-4199, 16 Jan 2023
- The Link Library WordPress plugin before 7.4.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2021-25091, 1 Feb 2022
- The Link Library WordPress plugin before 7.2.9 does not sanitise and escape the settingscopy parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting CVE record
- CVE-2021-25092, 1 Feb 2022
- The Link Library WordPress plugin before 7.2.8 does not have CSRF check when resetting library settings, allowing attackers to make a logged in admin reset arbitrary settings via a CSRF attack CVE record
- CVE-2021-25093, 1 Feb 2022
- The Link Library WordPress plugin before 7.2.8 does not have authorisation in place when deleting links, allowing unauthenticated users to delete arbitrary links via a crafted request CVE record
What to do if you run Link Library
If you run Link Library, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Link Library vulnerabilities
Free. We email you when a new vulnerability is published for Link Library, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.