CVE-2025-2719 MEDIUM

CVE-2025-2719: Swatchly – WooCommerce Variation Swatches for Products (product attributes: Image swatch, Color swatches, Label swatches) 1.2.8 - 1.4.0 - Missing Authorization to Authenticated (Subscriber+) Limited Options Update

Vendor Hasthemes
Product Swatchly – WooCommerce Variation Swatches for Products (product attributes: Image swatch, Color swatches, Label swatches)
Weakness CWE-862 · Missing authorization
Published April 10, 2025
Last update April 10, 2025

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The Swatchly – WooCommerce Variation Swatches for Products (product attributes: Image swatch, Color swatches, Label swatches) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the ajax_dismiss function in versions 1.2.8 to 1.4.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update option values to 1/true on the WordPress site. This can be leveraged to update an option that would create an error on the site and deny access to legitimate users or be used to set some values to true, such as registration.

Explanation of Vulnerability in Simple Terms

02Summary

Swatchly, a WooCommerce product attribute plugin, fails to properly check user permissions when modifying product variation swatches. A logged-in user with low privileges can change image, color, or label swatches on any product without authorization. This affects versions 1.2.8 through 1.4.0.

What an attacker can do

03Attacker Capabilities

Modify product variation swatches (images, colors, labels) on any WooCommerce product without proper authorization.

Potential impact on your site

04Site Impact

Unauthorized users can alter how product variations appear to customers, potentially disrupting sales or product presentation.

Conditions required to exploit

05Prerequisites

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

Key dates

06Disclosure timeline

April 10, 2025 CVE published
April 10, 2025 Record updated