A security vulnerability has been disclosed in Welcart e-Commerce, a WordPress-based online shopping platform widely used in Japan. The flaw, tracked as CVE-2026-119166, allows an unauthenticated attacker to change the email address and password associated with an existing customer account. This can potentially give the attacker complete control over the affected customer’s Welcart account without knowing the original login credentials.
The vulnerability affects Welcart e-Commerce versions up to and including 2.12.5. A security fix is available in version 2.12.6, released on October 23, 2026. The vulnerability was publicly disclosed on October 30, with the corresponding CVE record published on October 31, 2026.
Although the vulnerability has a CVSS score of 5.3, classified as medium severity, its potential consequences deserve particular attention from online store owners because the attack targets customer authentication and account ownership.
What Is CVE-2026-119166?
CVE-2026-119166 is an account takeover vulnerability caused by insufficient validation of user-controlled account identifiers in the Welcart e-Commerce plugin.
According to the vulnerability information published by Wordfence, the problem involves the member[ID] parameter used in Welcart’s customer registration and membership functionality.
In affected versions, the application does not adequately verify whether a user submitting an account-related request is authorized to modify the customer record identified by that parameter.
Consequently, an attacker may be able to target an existing customer account by supplying its numerical membership identifier.
The vulnerability is associated with an Insecure Direct Object Reference (IDOR) weakness and is classified under CWE-287, Improper Authentication.
Unlike vulnerabilities requiring administrator access or an existing customer account, this issue can be exploited without prior authentication.
How Can an Attacker Take Over a Welcart Customer Account?
The vulnerability affects the way Welcart processes customer information during registration-related operations.
Under normal circumstances, a customer should only be able to create a new account or update their own information after the application verifies their identity and authorization.
In vulnerable Welcart installations, the authorization checks do not sufficiently protect the relationship between the submitted membership identifier and the account being modified.
The documented attack scenario involves the following sequence:
- Identifying an existing customer account. The attacker targets a numerical membership identifier belonging to an existing Welcart customer.
- Submitting an unauthorized account update. A manipulated request is sent through the affected customer registration functionality.
- Overwriting account credentials. Due to insufficient validation, the application can accept changes to the targeted customer’s email address and password.
- Accessing the compromised account. The attacker can subsequently authenticate using the replacement credentials and obtain control of the affected Welcart membership account.
Importantly, the attacker does not need to know the victim’s original password or have access to their email inbox.
Wordfence also explains that the affected workflow uses a WordPress nonce validation mechanism. However, the relevant nonce is made available to unauthenticated visitors through the automatically published New Enrollment Form.
As a result, the nonce check does not provide an effective barrier against this particular unauthorized account modification.
The documented vulnerability does not require a non-default configuration or an existing WordPress login.
Why Is This Vulnerability Dangerous for Online Stores?
Customer accounts are an important part of many e-commerce operations. Depending on the platform configuration, they may contain personal information, contact details, delivery addresses, account preferences and purchase history.
Welcart includes its own customer membership system, allowing merchants to manage registered shoppers and their orders.
If an attacker successfully takes over a customer’s account, they may gain access to information or account functions available to that customer through the storefront.
The precise consequences depend on the store’s configuration and the information accessible within the affected account.
Potential operational consequences include:
- Loss of customer account control: the legitimate customer may be unable to sign in after their credentials have been replaced.
- Unauthorized account activity: the attacker may be able to use customer-facing functions while authenticated as the victim.
- Exposure of customer information: personal details or order information could be accessible if the compromised account provides access to those records.
- Customer support incidents: merchants may receive complaints about unexpected credential changes or inaccessible accounts.
- Damage to customer confidence: confirmed account compromises can undermine trust in the online store.
These are potential consequences of account takeover, not confirmation that customer information has already been stolen from vulnerable Welcart installations.
The flaw does not automatically grant WordPress administrator privileges, compromise the underlying server or provide direct access to payment card data stored by external payment processors.
Which Welcart Versions Are Vulnerable?
The confirmed affected version range includes all Welcart e-Commerce releases up to and including version 2.12.5.
| Security detail | Confirmed information |
|---|---|
| Vulnerability identifier | CVE-2026-119166 |
| Affected product | Welcart e-Commerce for WordPress |
| Vulnerable versions | 2.12.5 and earlier |
| Fixed version | 2.12.6 |
| CVSS v3.1 | 5.3 — Medium |
| Weakness classification | CWE-287 — Improper Authentication |
| Authentication required | No |
| User interaction required | No |
| Patch release date | October 23, 2026 |
| Public disclosure | October 30, 2026 |
| CVE publication | October 31, 2026 |
Welcart 2.12.6 addresses the account modification problem by strengthening membership update controls.
According to the official release notes, member information updates are restricted to the currently authenticated customer, and changes are no longer applied before the required email verification has been completed.
The same release also contains additional security improvements involving SQL injection, redirect validation, authorization checks and cross-site scripting protection.
These are separate security fixes included in the release and should not be confused with the specific account takeover vulnerability described by CVE-2026-119166.
The full list of changes is available in the official Welcart 2.12.6 release announcement.
How to Check Whether Your Store Is Affected
Store owners and administrators should verify whether their WordPress installation uses the Welcart e-Commerce plugin and, if so, which version is currently installed.
To check the installed version:
- Sign in to the WordPress administration dashboard.
- Open the Plugins → Installed Plugins section.
- Locate Welcart e-Commerce in the plugin list.
- Check the installed version number.
- If the version is 2.12.5 or earlier, arrange an update to version 2.12.6 or a later security-maintained release.
The issue is specific to Welcart e-Commerce. It should not be interpreted as a vulnerability affecting WordPress core, WooCommerce or every WordPress-based shopping website.
For merchants operating internationally, the same account security considerations apply whether they manage a single sklep internetowy (online store) or several sklepy internetowe (online stores) connected to shared business processes.
How to Secure Welcart Against CVE-2026-119166
The most important security measure is to update the affected plugin. Additional checks may help identify suspicious account changes that occurred before the update was installed.
1. Update Welcart e-Commerce to Version 2.12.6 or Later
Install the corrected release using the official WordPress plugin update mechanism or the distribution provided by Welcart.
Before performing the update on a production store, create a backup of the database and website files. Where possible, test the update in a staging environment, particularly if the store uses custom checkout functionality, additional payment integrations or modified customer registration forms.
After updating, confirm that the plugin version is no longer within the vulnerable range.
2. Review Customer Email and Password Changes
Administrators should investigate reports of unexpected account changes, particularly where customers claim that their email addresses or passwords have been modified without authorization.
If the store maintains sufficiently detailed application or security logs, examine unusual account registration and membership update activity.
Pay attention to repeated attempts to change customer details and suspicious activity involving multiple membership accounts.
The availability of such evidence depends on the website’s logging configuration. Standard WordPress installations do not necessarily maintain a complete historical record of all membership changes.
3. Investigate Potentially Compromised Accounts
Where unauthorized changes are confirmed or strongly suspected, administrators should take appropriate steps to secure the affected accounts.
These may include invalidating active sessions where supported, resetting account credentials through a trusted process and verifying the legitimate customer’s identity before restoring access.
Customer contact details should be checked carefully because the vulnerability specifically allows modification of the email address associated with an account.
Sending account recovery instructions to an unverified, recently changed email address could allow an attacker to retain control.
4. Test Customer Registration and Account Management
Following the update, test the main account-related functions:
- New customer registration.
- Email verification during account creation or modification.
- Customer login and logout.
- Password changes and password recovery.
- Updating personal details and delivery addresses.
- Access to order history and other membership features.
Testing should confirm that customers can only modify their own account information and that legitimate account changes continue to function correctly.
5. Keep Other E-commerce Components Updated
Welcart 2.12.6 contains several security corrections beyond CVE-2026-119166. This illustrates why updating only the main WordPress installation is not sufficient to protect an online business.
The security of an e-commerce website also depends on its shopping cart software, payment integrations, customer management components, themes and other extensions.
The official plugin version and change history can be reviewed in the WordPress plugin directory for Welcart e-Commerce.
Are Hackers Actively Exploiting CVE-2026-119166?
As of November 1, 2026, there is no confirmed public evidence of widespread active exploitation of CVE-2026-119166 against Welcart stores.
The published vulnerability record documents a credible account takeover scenario, but it does not establish that attackers have already compromised customer accounts in real-world incidents.
There is also an important distinction between the vulnerability’s technical severity rating and its potential consequences for an individual merchant.
The assigned CVSS score is 5.3, placing the issue in the medium-severity category. However, unauthorized changes to customer authentication credentials can still represent a significant operational and customer security problem.
The fact that no password or existing account is required to exploit the vulnerability increases the importance of promptly applying the available correction.
Why Account Authorization Matters in E-commerce Security
This vulnerability highlights a fundamental security requirement: applications must verify not only whether a request is technically valid, but also whether the person submitting it is authorized to modify the specific customer record.
A valid request token does not necessarily establish account ownership. Similarly, knowing or supplying a numerical customer identifier must never be sufficient to authorize changes to sensitive information.
Effective protection requires server-side authorization checks that associate each account modification with the properly authenticated and authorized customer.
For online retailers, these controls are especially important because customer accounts may provide access to personal information, order details and other services that should remain available only to the legitimate account holder.
Welcart Store Owners Should Update Without Delay
CVE-2026-119166 affects Welcart e-Commerce versions 2.12.5 and earlier and can allow unauthenticated attackers to overwrite customer email addresses and passwords through insufficient account authorization checks.
The vulnerability was publicly disclosed at the end of October 2026, while the corrective update had already been released on October 23.
Store administrators should ensure that Welcart 2.12.6 or later is installed, review potentially suspicious account modifications and verify that customer registration and account recovery functions operate correctly.
No active exploitation campaign has been publicly confirmed, but the availability of a documented account takeover mechanism makes prompt remediation important for merchants using affected versions.
The technical vulnerability description, CVSS assessment and affected version range are available in the Wordfence Intelligence advisory for CVE-2026-119166.