The Link Library WordPress plugin before 7.10.0 does not re-check the selected library's own login requirement when
Source GCVE Database
Not known to be exploited : upgrade to 7.10.0 when convenient.
Data as of 29 Oct 2026, 07:09 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 7.10.0
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Link Library (WordPress plugin) to 7.10.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Link Library | Affected
| Fixed in
|
AI-suggested
A fix is available in version 7.10.0 of the Link Library WordPress plugin. Users should upgrade to version 7.10.0 or later to remediate this vulnerability. No other mitigation steps are indicated.
Description
The Link Library WordPress plugin versions prior to 7.10.0 contain a vulnerability where the plugin fails to re-check the login requirement of the selected library during front-end link submissions. This flaw allows unauthenticated users to submit links to libraries that are configured to require login by reusing a form token from another library that does not require login.