Tune Library Plugin up to 1.6.3 on WordPress Shortcode authorization

Summaryinfo

A vulnerability was found in Tune Library Plugin up to 1.6.3 on WordPress. It has been rated as problematic. This vulnerability affects unknown code of the component Shortcode Handler. Performing a manipulation results in authorization. This vulnerability is cataloged as CVE-2026-1401. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Tune Library Plugin up to 1.6.3 on WordPress. It has been classified as problematic. This affects an unknown function of the component Shortcode Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2026-1401. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/06/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Software Library

Name

• Tune Library Plugin

Version

• 1.6.0
• 1.6.1
• 1.6.2
• 1.6.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion