Security readout for executives and security teams
Plain-English summary
CVE-2022-3995 lets any logged-in WordPress user with subscriber-level access or higher lock or unlock other users' WooCommerce wallet accounts in vulnerable TeraWallet releases. The issue is not a full site takeover, but it can disrupt wallet availability and interfere with customer account operations.
Executive priority
Treat this as a medium-priority ecommerce integrity issue. It is unlikely to compromise the whole site, but it can create customer disruption or operational abuse where wallet features support purchases, credits, or refunds.
Technical view
The vulnerability is an insecure direct object reference in the lock_unlock_terawallet AJAX action. The plugin insufficiently validates a user-controlled key, allowing low-privileged authenticated users to affect another user's wallet lock state. Sources rate it CVSS 4.3 with low integrity impact and no confidentiality or availability impact in the CVSS model.
Likely exposure
Exposure is limited to WordPress sites running TeraWallet or Wallet for WooCommerce versions up to and including 1.4.3, with attacker access to any authenticated account at subscriber level or higher.
Exploitation context
The source bundle does not show known active exploitation, and CISA KEV is false. Abuse requires authentication, but many WooCommerce sites allow customer or subscriber registration, which can lower the practical barrier.
Researcher notes
Focus validation on authorization checks around lock_unlock_terawallet and whether attacker-controlled identifiers can target another user's wallet. Avoid assuming broader wallet balance manipulation; the provided sources only support lock and unlock impact.
Mitigation direction
- Identify sites running TeraWallet or Wallet for WooCommerce.
- Update affected plugin installations after confirming vendor guidance.
- Disable or restrict public user registration where business workflows allow.
- Remove unnecessary low-privileged WordPress accounts.
- Monitor wallet lock and unlock activity for suspicious changes.
Validation and detection
- Check installed plugin versions against the affected range through 1.4.3.
- Confirm whether public customer or subscriber registration is enabled.
- Review wallet state changes for unexpected lock or unlock events.
- Verify vendor changelog or WordPress plugin updates include the referenced fix.
- Retest access controls after updating or applying vendor guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-3995 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ec57e0b2-61b0-4b67-9784-dbb4e6c4e4a6?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset/2817824/woo-wallet/trunk?contextall=1&old=2816610&old_path=%2Fwoo-wallet%2FtrunkCVE reference
- https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-3995CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.