CVE-2026-119166
The Welcart e-Commerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.12.5 via the 'member[ID]' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to overwrite any existing Welcart shop-member account's email address and password by supplying that member's numeric ID, then authenticate as that member to achieve full account takeover. The only authentication barrier is a wp_verify_nonce() check against a nonce printed to every unauthenticated visitor on the auto-published New Enrollment Form, meaning no existing account, no WordPress login, and no non-default configuration is required to exploit this vulnerability.
Executive briefing
This record describes a reported software or hardware weakness. The description and CVSS rating are source metadata; practical risk depends on whether your environment uses an affected product/version and whether the vulnerable component is reachable and configured in an exploitable way.
Severity & exploitability
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Impacted products and platforms
Specific affected product configurations are not currently available in the NVD record. Review vendor advisories and validate applicability against your asset inventory.
How it works and what it could affect
The NVD description is the authoritative short summary currently available for this record. A detailed technical mechanism is not inferred when the source record does not provide one.
Weakness classification: CWE-287
Review the CVSS attack characteristics above to understand whether exploitation is network/local, whether privileges or user interaction are required, and which confidentiality, integrity or availability impacts are scored.
Remediation and recommended response
- Identify exposure: compare the affected product and version ranges below with your asset inventory, software bill of materials, endpoint inventory and externally exposed services.
- Remediate: review the linked vendor security advisory or patch notes, upgrade to a fixed release, or apply the vendor-provided workaround if an upgrade cannot be completed.
- Mitigate while patching: restrict network access to the vulnerable service, disable the affected feature where operationally safe, and monitor vendor/CERT advisories for updated guidance.
- Validate: confirm the fixed version or mitigation on representative systems, run a vulnerability rescan, and retain change evidence.
Vendor remediation / security advisories
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
- security@wordfence.com — vendor
Exploit intelligence & references
No CISA KEV match is recorded in the latest successful catalog refresh. This is not a guarantee that public proof-of-concept code or exploitation does not exist.
- security@wordfence.com vendor
- security@wordfence.com vendor
- security@wordfence.com vendor
- security@wordfence.com vendor
- security@wordfence.com vendor
- security@wordfence.com vendor
- security@wordfence.com reference
Sources: NVD and CISA KEV when available. Vendor confirmation remains the final authority for fixed versions and workarounds.