Security readout for executives and security teams
Plain-English summary
A logged-in WordPress user with subscriber-level access could reach data they should not be allowed to access through the Customer Reviews for WooCommerce plugin. The issue is limited in severity because it requires an account and is described as low confidentiality impact, but exposed ecommerce sites should still treat affected versions as a real privacy and trust risk.
Executive priority
Prioritize this as a moderate-risk ecommerce hygiene issue. It is not currently supported as actively exploited in the supplied sources, but affected public WordPress stores with many customer accounts should remediate promptly because the flaw concerns access control and possible data exposure.
Technical view
CVE-2022-38134 is an authenticated broken access control issue in CusRev Customer Reviews for WooCommerce versions 5.3.5 and earlier. CVSS 3.1 is 4.3 with network access, low attack complexity, low privileges, no user interaction, unchanged scope, and low confidentiality impact only. The supplied sources do not identify the exact vulnerable endpoint or a fixed version.
Likely exposure
Exposure is limited to WordPress sites running Customer Reviews for WooCommerce version 5.3.5 or earlier, where an attacker has at least subscriber-level authentication. Public ecommerce sites with open registration or many customer accounts have higher practical exposure than sites without user self-registration.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation would require a valid low-privilege account but no user interaction. No exploit details, vulnerable request path, or weaponized proof are provided in the supplied sources.
Researcher notes
The public bundle establishes affected product, version range, CWE category, privilege requirement, and CVSS. It does not provide enough detail to validate the vulnerable code path or confirm a specific patched release. Avoid assuming broader WooCommerce, WordPress core, or unauthenticated exposure without additional vendor evidence.
Mitigation direction
- Inventory WordPress sites for Customer Reviews for WooCommerce installations.
- Treat plugin versions 5.3.5 and earlier as affected.
- Check vendor, WordPress.org, or Patchstack guidance for the patched version.
- Update the plugin through normal WordPress maintenance controls when guidance confirms availability.
- Disable the plugin temporarily if affected and business risk outweighs functionality.
- Review and remove unnecessary low-privilege WordPress accounts.
Validation and detection
- Confirm installed plugin name and version on each WordPress site.
- Compare findings against the affected range: 5.3.5 and earlier.
- Check whether public registration or customer account creation is enabled.
- Review plugin changelog and Patchstack entry for remediation status.
- Look for unusual authenticated access to review or plugin-related functionality.
- Document whether compensating access controls are in place.
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-264: 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-38134 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:L/I:N/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:L/I:N/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:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/customer-reviews-woocommerce/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/customer-reviews-woocommerce/wordpress-customer-reviews-for-woocommerce-plugin-5-3-5-authenticated-broken-access-control-vulnerability/_s_id=cveCVE reference · x_refsource_CONFIRM
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.
Permissions, Privileges, and Access Controls
Permissions, Privileges, and Access Controls represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.