CVE-2026-57422
Deferred Deferred - Pending Action

Cross-Site Scripting in Bopo WooCommerce Product Bundle Builder

Vulnerability report for CVE-2026-57422, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Patchstack

Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in VillaTheme Bopo – WooCommerce Product Bundle Builder bopo-woo-product-bundle-builder allows Reflected XSS.This issue affects Bopo – WooCommerce Product Bundle Builder: from n/a through <= 1.2.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-13
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
villatheme bopo_woocommerce_product_bundle_builder to 1.2.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Cross Site Scripting (XSS) issue found in the WordPress plugin "Bopo – WooCommerce Product Bundle Builder" version 1.2.0 or earlier. It occurs because the plugin improperly neutralizes input during web page generation, allowing attackers to inject malicious scripts into the website.

Exploitation requires user interaction, such as clicking a malicious link or submitting a form, which then reflects the malicious script back to the user.

Detection Guidance

This vulnerability is a reflected Cross Site Scripting (XSS) issue in the Bopo – WooCommerce Product Bundle Builder plugin version 1.2.0 or earlier. Detection typically involves monitoring for suspicious HTTP requests that include malicious script payloads in URL parameters or form submissions.

You can detect potential exploitation attempts by inspecting web server logs for unusual query strings or payloads containing script tags or JavaScript code.

Example commands to search for suspicious patterns in Apache or Nginx logs might include:

  • grep -iE "<script|javascript:" /var/log/apache2/access.log
  • grep -iE "<script|javascript:" /var/log/nginx/access.log

Additionally, using web application firewalls (WAF) with rules targeting reflected XSS payloads can help detect and block attempts.

Impact Analysis

If exploited, this vulnerability can allow attackers to execute malicious scripts in the context of the affected website. This can lead to unauthorized actions such as stealing user credentials, session hijacking, or delivering malware to users.

The vulnerability has a CVSS score of 7.1, indicating a moderate level of risk, and it can be exploited in mass campaigns if users interact with malicious content.

Compliance Impact

This vulnerability, a Reflected Cross-Site Scripting (XSS) issue, can impact compliance with standards and regulations like GDPR and HIPAA due to its potential to expose sensitive data or allow unauthorized actions.

  • GDPR: If the vulnerable plugin is used on a website processing personal data of EU citizens, successful exploitation could lead to unauthorized access or theft of personal data. This violates GDPR's requirements for data protection and confidentiality (Articles 5, 32).
  • HIPAA: For healthcare-related websites using this plugin, the vulnerability could expose protected health information (PHI) if an attacker injects malicious scripts to steal or manipulate data. This violates HIPAA's Security Rule, which mandates safeguards for electronic PHI.
  • Non-compliance risks include regulatory fines, legal liabilities, and reputational damage, especially if the vulnerability is exploited to compromise user data or system integrity.

Organizations using the affected plugin should apply the patch immediately to mitigate risks and ensure compliance with applicable regulations.

Mitigation Strategies

The immediate and recommended mitigation step is to update the Bopo – WooCommerce Product Bundle Builder plugin to version 1.2.1 or later, where the vulnerability is patched.

Until the update can be applied, it is advised to implement the mitigation rule provided by Patchstack to block attack attempts targeting this vulnerability.

Additionally, consider deploying or tuning a web application firewall (WAF) to detect and block reflected XSS payloads.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57422. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart