CVE-2025-14875
Reflected XSS in HBLPAY WooCommerce Plugin Allows Script Injection
Publication date: 2026-01-07
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | hblpay_payment_gateway_for_woocommerce | to 5.0.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the HBLPAY Payment Gateway for WooCommerce plugin is a Reflected Cross-Site Scripting (XSS) issue via the 'cusdata' parameter. This occurs because the plugin does not properly sanitize or escape input from this parameter, allowing unauthenticated attackers to inject arbitrary web scripts. These scripts can execute in the context of a user's browser if the user is tricked into clicking a malicious link, potentially compromising their session or data.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts in the browsers of users interacting with your WooCommerce site using the HBLPAY Payment Gateway plugin. This can lead to theft of user credentials, session hijacking, defacement of the website, or redirection to malicious sites. Since the attack requires tricking a user into clicking a crafted link, it can be used for phishing or other social engineering attacks, potentially damaging your site's reputation and user trust.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing for Reflected Cross-Site Scripting (XSS) via the 'cusdata' parameter in the HBLPAY Payment Gateway for WooCommerce plugin. You can attempt to inject a simple script payload into the 'cusdata' parameter in URLs or forms handled by the plugin and observe if the script executes in the user's browser. For example, you can use curl or a browser to send a request with a payload like <script>alert(1)</script> in the 'cusdata' parameter and check if it is reflected unsanitized in the response. Example command: curl -G 'https://yourdomain.com/path-to-plugin-endpoint' --data-urlencode 'cusdata=<script>alert(1)</script>' -v. Monitoring web server logs for suspicious requests containing script tags in the 'cusdata' parameter can also help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Updating the HBLPAY Payment Gateway for WooCommerce plugin to a version later than 5.0.0 where the vulnerability is fixed. 2) If an update is not immediately available, consider disabling the plugin temporarily to prevent exploitation. 3) Implement Web Application Firewall (WAF) rules to block or sanitize requests containing suspicious script payloads in the 'cusdata' parameter. 4) Educate users to avoid clicking on suspicious links that may exploit this reflected XSS vulnerability. 5) Monitor logs for exploitation attempts and respond accordingly.