On October 22, 2026, a newly published advisory described a stored cross-site scripting flaw in the WordPress Link Library plugin. The Link Library XSS vulnerability affects versions before 7.9.6 and involves crafted link data rendered inside a preview.
If you manage a site that uses Link Library, check its installed version and update to 7.9.6 or later. The reported issue requires a user who can submit a link, but the preview does not require authentication to view and may include an unapproved submission.
In brief: Link Library versions before 7.9.6 do not properly sanitize and escape a link field before placing it in a preview attribute. A Contributor or higher can submit crafted data, and a visitor who opens the resulting preview may encounter stored script. Update the plugin to version 7.9.6 or later; the WordPress.org changelog says that release fixed security issues.
What the Link Library XSS vulnerability does
The advisory identifies the issue as CVE-2026-78392. It says the plugin fails to sanitize and escape a link field before outputting it inside an attribute in a link preview. The resulting stored XSS can run in a visitor’s browser when the preview is rendered.
The report describes the access needed as Contributor or higher. It also says the preview is generated without authentication and without checking whether the submitted link has been published. That distinction matters: an unapproved submission may still be included in a preview that visitors can open.
The advisory lists the issue as medium severity, with a CVSS 3.1 score of 6.8. It does not report active exploitation, name a specific function or endpoint, or claim that every Link Library installation is exposed in the same way. The documented affected range is versions before 7.9.6.
Which Link Library versions are affected?
According to the October 22 advisory, Link Library releases earlier than 7.9.6 are affected. WPScan’s plugin record lists 10,000 active installations and also identifies 7.9.6 as the version that fixed this reported issue.
The plugin’s WordPress.org changelog says version 7.9.6 fixed potential security issues reported by Karthik Ramakrishnan, Daria Golikova, Osman Hussein and Charles Vosburgh. It does not describe the individual fixes in that entry, so the changelog alone does not establish which change addresses CVE-2026-78392.
Link Library is used to display categorized lists of links on WordPress pages. The plugin documentation describes using shortcodes to show link lists and categories. For site owners, the reported flaw is most relevant where people other than administrators can submit links and visitors can open previews.
What site owners should do
Check the Link Library version on every site you maintain. If it is below 7.9.6, update to 7.9.6 or a later version. If the plugin is not in use, review whether it should remain installed; the advisory does not say that deactivation is required for sites already on a fixed release.
After updating, confirm the plugin reports the expected version in the WordPress dashboard. If your site accepts link submissions from contributors, review that workflow and consider whether unapproved submissions can be previewed by visitors. That check follows directly from the behavior described in the advisory, but the report does not provide a separate mitigation for sites that cannot update.
The advisory does not identify active attacks or provide indicators of compromise. Avoid treating this as evidence that a site has been breached. The practical response is to identify installations below the fixed version and apply the update.
Why the preview behavior matters
Stored XSS differs from a flaw that only reflects data from a single crafted request: the report says submitted link data is stored and then appears in a preview. It also says an unauthenticated visitor can view the preview, even when the submitted link has not been published. That can widen who might encounter the malicious content, depending on how a site uses previews.
The advisory does not say that simply visiting a site triggers the flaw, nor does it describe automatic compromise. A visitor must open the preview for the script to be rendered, according to the report. Keep that distinction in mind when assessing urgency and explaining the issue to editors.
FAQ
What is the fixed version for the Link Library flaw?
The reported affected versions are those before 7.9.6. Update to Link Library 7.9.6 or later.
Does exploiting the flaw require an administrator account?
No. The advisory says a user with Contributor privileges or higher can submit a crafted link. It says the preview can be viewed without authentication.
Is the Link Library vulnerability being actively exploited?
The advisory does not report active exploitation. It describes a stored XSS issue and assigns it a medium CVSS 3.1 score of 6.8.
Next step: Check the Link Library version on each WordPress site you manage and update any installation below 7.9.6.