CVE-2025-14875 MEDIUM

CVE-2025-14875: HBLPAY Payment Gateway for WooCommerce <= 5.0.0 - Reflected Cross-Site Scripting via 'cusdata' Parameter

Vendor Hblpay
Product HBLPAY Payment Gateway for WooCommerce
Weakness CWE-79 · XSS
Published January 7, 2026
Last update April 8, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The HBLPAY Payment Gateway for WooCommerce plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘cusdata’ parameter in all versions up to, and including, 5.0.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

The HBLPAY Payment Gateway for WooCommerce contains a cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts into pages viewed by site visitors. An attacker can craft a malicious link or page that, when visited by a user, executes JavaScript in their browser within the context of your WooCommerce site. This can lead to session hijacking, credential theft, or unauthorized actions on behalf of the victim.

What an attacker can do

03Attacker Capabilities

Inject and execute malicious JavaScript in visitors' browsers to steal session tokens, credentials, or perform actions as the victim.

Potential impact on your site

04Site Impact

Visitors to your WooCommerce store may have their sessions hijacked or credentials stolen if they interact with attacker-controlled content.

Conditions required to exploit

05Prerequisites

Attacker needs to trick a site visitor into clicking a malicious link or visiting a compromised page (user interaction required).

Key dates

06Disclosure timeline

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

Related vulnerabilities

08Related CVE