CVE-2026-120049 json
Link Library <= 7.10.0 - Unauthenticated Stored Cross-Site Scripting via File Upload Filename
published 10h ago modified 5h ago also EUVD-2026-128997
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-120049 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- jackdewey Link Library
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/0f4cef04-d78c-4afb-bbb9-6de0ab295cbd?source=cve
- plugins.trac.wordpress.org /browser/link-library/tags/7.10.0/usersubmission.php#L476
- plugins.trac.wordpress.org /browser/link-library/tags/7.10.0/rsspreview.php#L59
- plugins.trac.wordpress.org /browser/link-library/tags/7.10.0/link-library.php#L2317
- plugins.trac.wordpress.org /browser/link-library/tags/7.10.0/usersubmission.php#L478
- plugins.trac.wordpress.org /browser/link-library/tags/7.10.1
Sources
- CVE List CVE-2026-120049
- NVD CVE-2026-120049
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.