CVE-2025-15019 MEDIUM

CVE-2025-15019: BIALTY - Bulk Image Alt Text (Alt tag, Alt Attribute) with Yoast SEO + WooCommerce <= 2.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

Vendor Pagup
Product Bulk Auto Image Alt Text (Alt tag, Alt attribute) optimizer (image SEO)
Weakness CWE-79 · XSS
Published January 9, 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 BIALTY - Bulk Image Alt Text (Alt tag, Alt Attribute) with Yoast SEO + WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'bialty_cs_alt' post meta in all versions up to, and including, 2.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the post editor.

Explanation of Vulnerability in Simple Terms

02Summary

The Bulk Auto Image Alt Text optimizer plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in versions up to 2.2.1. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site users, potentially compromising admin accounts or stealing sensitive data. The vulnerability affects the site's scope, meaning impacts extend beyond the plugin itself.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers, potentially stealing credentials or session tokens.

Potential impact on your site

04Site Impact

Any authenticated user can inject code affecting other users; admins are at risk of account compromise.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., contributor or subscriber role).

Key dates

06Disclosure timeline

January 9, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE