CVE-2026-1401 MEDIUM

CVE-2026-1401: Tune Library <= 1.6.3 - Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting via CSV Import

Vendor Jackdewey
Product Tune Library
Weakness CWE-79 · XSS
Published February 6, 2026
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Tune Library versions up to 1.6.3 contain a cross-site scripting (XSS) vulnerability that allows authenticated users to inject malicious scripts. The vulnerability has a changed scope, meaning the impact can extend beyond the vulnerable component to affect other parts of a site or other users. Low-level authentication is required to exploit this issue.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in other users' browsers or affect other site components.

Potential impact on your site

04Site Impact

Authenticated users can inject scripts affecting other users or site functionality; data theft or account compromise possible.

Conditions required to exploit

05Prerequisites

Attacker must have a low-level user account on the site; no user interaction required.

Key dates

06Disclosure timeline

February 6, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE