dbcve.org
Sales Report Email For WoocommerceWordPress extension · Zorem

CVE-2022-38141

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-17
Fix available
A fix is available. Upgrade to after 2.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing Authorization vulnerability in Zorem Sales Report Email for WooCommerce.This issue affects Sales Report Email for WooCommerce: from n/a through 2.8.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Missing Authorization (Broken Access Control) vulnerability in the Zorem Sales Report Email for WooCommerce plugin. The vulnerability allows low-privileged users to potentially access or perform actions that should require higher-level permissions due to missing capability checks before executing sensitive operations.

MitigationUpdate the plugin to version 2.8 or later which should contain proper authorization/capability checks. Until then, limit user access to only trusted, high-privilege users and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sales Report Email For WoocommerceWordPress extension
Affected:<= 2.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin installation
    Check your WordPress wp-content/plugins directory for a folder named 'sales-report-email-for-woocommerce' or similar Zorem plugin folder
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed version
    Open the main plugin PHP file and locate the version comment/constant, or check the WordPress plugin admin page for the installed version number
    Affected if The version number is 2.8 or lower
  3. Confirm the plugin is active
    Navigate to WordPress Admin > Plugins and verify the Sales Report Email for WooCommerce plugin is activated
    Affected if The plugin shows as active in the WordPress admin panel
  4. Check for missing capability checks in plugin code
    Review the plugin source code for AJAX handlers or admin pages that process requests without using current_user_can() or check_admin_referer() before performing sensitive operations
    Affected if Sensitive functions (such as report generation, email sending, or data export) lack capability verification checks

You are affected if the Zorem Sales Report Email for WooCommerce plugin is installed, active, and running version 2.8 or lower without proper authorization/capability checks in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.8
Interim mitigation

Update the plugin to version 2.8 or later which should contain proper authorization/capability checks. Until then, limit user access to only trusted, high-privilege users and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Update to the latest version available in the WordPress plugin repository (version greater than 2.8)

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Sales Report Email for WooCommerce' by Zorem
  4. Check the current installed version to confirm it is 2.8 or lower
  5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  6. After updating, verify the new version number in the Plugins list
  7. Test that the Sales Report Email functionality continues to work correctly
  8. Ensure that only authorized users have access to the Sales Report Email features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sales Report Email For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38141 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data