CVE-2026-57358: Unauthenticated XSS in Customize My Account for WooCommerce ≤4.3.9
A cross-site scripting (XSS) vulnerability exists in Customize My Account for WooCommerce versions 4.3.9 and earlier. An attacker can inject malicious scripts into the plugin without needing authentication, which are then executed in the browsers of site visitors. This happens because user input is not properly validated or sanitized before being reflected in the page. A victim would need to click a malicious link or visit a compromised page, but once they do, the attacker gains the ability to steal session cookies, capture credentials, or perform unauthorized actions on behalf of the logged-in user.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.1 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-02 / 2026-07-02
NVD description (verbatim)
Unauthenticated Cross Site Scripting (XSS) in Customize My Account for WooCommerce <= 4.3.9 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-57358 is an unauthenticated reflected XSS vulnerability (CWE-79) in the Customize My Account for WooCommerce plugin affecting version 4.3.9 and below. The vulnerability stems from insufficient input validation and output encoding in the plugin's handling of user-supplied data. Because the plugin does not properly escape or sanitize untrusted input before rendering it in HTML context, an attacker can craft a specially formatted URL or form submission that causes arbitrary JavaScript to execute within the victim's browser session. The attack vector is network-based with low complexity, requires no privileges, but does necessitate user interaction (clicking a link). With a CVSS score of 7.1 (HIGH), the impact spans confidentiality, integrity, and availability within the context of the affected browser session and site.
Business impact
For WooCommerce store operators, this vulnerability can lead to customer account compromise, credential theft, and unauthorized transactions. An attacker could redirect customers to phishing pages, steal authentication tokens, or modify account details (addresses, payment methods) without the store operator's knowledge. The reputational damage from customer data exposure or fraudulent activity conducted through compromised accounts can erode trust and result in chargebacks. Additionally, if the XSS is chained with other vectors, it could facilitate more sophisticated attacks such as supply chain compromises or widespread malware distribution via the store.
Affected systems
The Customize My Account for WooCommerce plugin versions 4.3.9 and earlier are affected. Any WooCommerce installation running this plugin at or below the affected version is at risk. The vulnerability does not require the attacker to have administrative access to the store; it is exploitable by unauthenticated actors via crafted URLs or injected content. Patched versions above 4.3.9 are not affected; store operators should verify their installed version against the plugin repository or their update notifications.
Exploitability
This vulnerability is relatively straightforward to exploit due to its low attack complexity and lack of authentication requirements. An attacker can distribute a malicious link via email, social media, forums, or comment sections on the store itself. When a customer clicks the link, the XSS payload executes immediately in their browser with their current session privileges. No advanced techniques are needed; basic URL encoding and JavaScript payloads suffice. However, exploitation requires the victim to interact with the malicious link, which lowers the attack surface compared to fully unauthenticated remote code execution but remains a practical threat in targeted or mass-phishing scenarios.
Remediation
Store operators must immediately upgrade Customize My Account for WooCommerce to a version newer than 4.3.9. The plugin should be updated through the WordPress admin dashboard or manually via the plugin repository. After patching, verify that the plugin version number reflects the update and test critical customer-facing workflows to ensure compatibility. As an interim measure while planning the upgrade, administrators should review access logs for suspicious query strings or unexpected parameter usage that might indicate exploitation attempts.
Patch guidance
Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate Customize My Account for WooCommerce, and check the current version. If it shows 4.3.9 or lower, click the update button if available, or manually download the latest version from the WordPress plugin repository. After updating, verify the new version number in the plugin list and perform a quick functional test of customer account pages. If automatic updates are disabled, prioritize this plugin in your update queue. For stores with custom modifications to the plugin, consult your developer before upgrading to ensure compatibility.
Detection guidance
Monitor web server logs and WAF (Web Application Firewall) logs for unusual query strings or POST parameters containing JavaScript syntax (e.g., <script>, onerror=, onload=, javascript:). Watch for patterns matching common XSS payloads such as event handlers or HTML tags in plugin-specific parameter names. Check access logs for repeated failed attempts to reach plugin endpoints with suspicious input. If you lack WAF capabilities, review HTTP requests to pages served by the Customize My Account plugin for unexpected HTML entities, script tags, or encoded JavaScript. Customer reports of unexpected redirects or altered account pages can also signal active exploitation.
Why prioritize this
With a CVSS score of 7.1 and direct impact on customer trust and transaction security, this vulnerability should be prioritized for immediate patching. Although the KEV program has not yet flagged it, the low barrier to exploitation and high business impact on e-commerce operations warrant urgent action. Any WooCommerce store using this plugin should treat it as a critical update candidate, especially those processing sensitive customer data or high transaction volumes.
Risk score, explained
The CVSS 7.1 (HIGH) score reflects the combination of an unauthenticated attack vector (AV:N), low attack complexity (AC:L), no required privileges (PR:N), and required user interaction (UI:R). The scope is changed (S:C), meaning the impact affects resources beyond the vulnerable component (other users' sessions, store reputation). The confidentiality, integrity, and availability impacts are all rated low (C:L, I:L, A:L) per the CVSS model because the attacker can typically affect one user per attack and the impact is limited to that session context, not the entire system. However, in aggregate across many customers, the business risk is substantial.
Frequently asked questions
How can I tell if my WooCommerce store is vulnerable?
Check your installed plugins list in the WordPress admin dashboard. Navigate to Plugins > Installed Plugins and search for 'Customize My Account for WooCommerce.' If the version displayed is 4.3.9 or lower, your store is vulnerable. You can also hover over the plugin name to see the exact version number. If the plugin is not installed, you are not affected.
Can this vulnerability be exploited without the attacker knowing my store URL?
No, the attacker needs to target your store specifically. They would craft a malicious link pointing to your WooCommerce store's domain that includes the XSS payload. However, the attacker does not need administrative access or valid credentials—they just need a way to distribute the malicious link to your customers (e.g., via email, social engineering, or ad networks).
What should I do if I suspect customers have been compromised?
First, update the plugin immediately to patch the vulnerability. Then, review your web server logs for suspicious activity around the plugin's endpoints during the suspected timeframe. Consider notifying customers to reset their passwords and monitor their accounts for unauthorized changes. If you handle sensitive data, you may be obligated by privacy regulations to notify affected users formally. Consult your legal and incident response team for guidance specific to your jurisdiction.
Is updating the plugin enough, or do I need to take additional security steps?
Updating is the primary remediation. However, best practices include auditing user accounts for unauthorized modifications, reviewing transaction logs for fraud, monitoring for follow-up attacks, and ensuring your WAF or security plugin is actively filtering malicious input. Also consider implementing Content Security Policy (CSP) headers to mitigate XSS impact site-wide, and ensure all other plugins and WordPress core are kept current.
This analysis is provided for informational purposes to assist security professionals in vulnerability management and risk prioritization. The information herein reflects the state of the vulnerability as of the publication date and is based on vendor advisories and technical research. SEC.co does not guarantee the completeness or accuracy of all details and recommends verification against official vendor security bulletins and your own environment testing before deploying patches. No warranty is provided regarding patch effectiveness or compatibility in all configurations. Always test patches in a staging environment before production deployment. For the most current and authoritative information, consult the official WordPress plugin repository and the plugin vendor's security advisories. Source: NVD (public-domain), retrieved 2026-08-11. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20066HIGHWordPress CP Polls 1.0.8 Persistent XSS Vulnerability
- CVE-2016-20084HIGHWordPress Appointment-Booking-Calendar Unauthenticated XSS and Privilege Escalation
- CVE-2023-33999HIGHDOM-Based XSS in WP Mail Log Plugin – Analysis & Remediation
- CVE-2023-45795HIGHXSS in Pilz PASvisu Builder Component – Patch Guidance
- CVE-2023-45796HIGHStored XSS in Pilz PASvisu & PMI Industrial Software – Remediation Guide
- CVE-2023-54351HIGHStored XSS in WordPress Sonaar Music Plugin 4.7 – Patch & Detection Guide
- CVE-2025-11262HIGHLink Whisper Free Stored XSS Vulnerability – Analysis & Patch Guidance
- CVE-2025-14773HIGHABB T-MAC Plus XSS Vulnerability – HIGH Risk Assessment