Is Tune Library safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.6.4). As of 2026-11-04. 2 issues are on record for older versions; version 1.6.4 or newer fixes all of them that state a fix. Keep Tune Library on the latest version (1.6.4) and remove it if you do not use it.

Which versions of Tune Library are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (1.6.3 and older, fixed in 1.6.4); SQL injection (1.5.4 and older, fixed in 1.6.3). The full list with sources is on this page.

What is the latest version of Tune Library?

1.6.4, according to wordpress.org (last updated 2026-02-01). It has 20+ active installs.

What should I do if my Tune Library is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update tune-library). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · tune-library · data as of 2026-11-04

Is Tune Library safe? Known vulnerabilities and latest version

Latest version: 1.6.4
Last updated: 2026-02-01
Active installs: 20+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 6.9.11

Import your iTunes music list into Wordpress and display your song collection on any page. — by Yannick Lefebvre

What to do

Update to the latest version (1.6.4). Anything older than 1.6.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get tune-library --field=version shows what you run; wp plugin update tune-library updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.4 CVE-2026-1401 · published 2026-02-06

Stored cross-site scripting (XSS) in Tune Library (1.6.3 and older)

Affected: 1.6.3 and older
Fixed in: 1.6.4 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Tune Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via CSV import in all versions up to, and including, 1.6.3. This is due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the injected page. The vulnerability exists because the CSV import functionality lacks authorization checks and doesn't sanitize imported data, which is later rendered without escaping through the [tune-library] shortcode.

NVD CVE-2026-1401 Wordfence advisory Code change (fix)Plugin source

high 8.1 CVE-2015-3314 · published 2017-09-07

SQL injection in Tune Library (1.5.4 and older)

Affected: 1.5.4 and older
Fixed in: 1.6.3 *
Access needed (per CVSS): No login needed
Range from: NVD analysis · score by NVD

Details from the advisory

SQL injection vulnerability in WordPress Tune Library plugin before 1.5.5.

NVD CVE-2015-3314 wordpress.org packetstormsecurity.com openwall.com openwall.com securityfocus.com exploit-db.com

Recent activity

2026-02-01 — latest release on wordpress.org (1.6.4).
2026-02-06 — Stored cross-site scripting (XSS) disclosed (CVE-2026-1401), fixed in 1.6.4.
2017-09-07 — SQL injection disclosed (CVE-2015-3314), fixed in 1.6.3.

Free. We check the CVE feeds every day and email you only when a new issue for Tune Library (tune-library) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (1) · SQL injection (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/tune-library (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/tune-library"><img src="https://laskyr.com/plugins/tune-library/badge.svg" alt="Tune Library vulnerability status"></a>

← Check another plugin · Free hacked-site scan