dbcve.org
Email Marketing For WoocommerceWordPress extension · Omnisend

CVE-2023-47244

HIGH · 7.5 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to 1.13.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Omnisend Email Marketing for WooCommerce by Omnisend.This issue affects Email Marketing for WooCommerce by Omnisend: from n/a through 1.13.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

The Omnisend Email Marketing plugin for WooCommerce versions up to 1.13.8 contains an information disclosure vulnerability allowing unauthorized actors to access sensitive information. The specific mechanism and exact data exposed are not detailed in available documentation, but the CVSS 7.5 score indicates significant risk of sensitive data exposure.

MitigationUpgrade to version 1.13.9 or later. Review access controls and ensure all endpoints handling sensitive customer or order data properly authenticate and authorize requests.

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
Email Marketing For WoocommerceWordPress extension
Affected:< 1.13.9

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Omnisend plugin version
    Access your WordPress admin panel, navigate to Plugins > Installed Plugins, and find 'Omnisend Email Marketing for WooCommerce' in the list. The version number is displayed below the plugin name.
    Affected if The displayed version is lower than 1.13.9 (for example, 1.13.8, 1.13.7, etc.)
  2. Check plugin file header version
    If you have file system access, locate the main plugin file typically named 'omnisend-for-woocommerce.php' within the /wp-content/plugins/omnisend-woocommerce/ directory. Open the file and locate the 'Version:' header comment at the top.
    Affected if The Version header value is less than 1.13.9
  3. Review WordPress plugins API
    If you have administrative API or database access, query the wp_options table or use WP-CLI with command: wp plugin list --name='omnisend-woocommerce'
    Affected if The returned version field shows a version below 1.13.9

You are affected if the installed Omnisend Email Marketing for WooCommerce plugin version is anything below 1.13.9, as the information disclosure vulnerability exists in all prior versions.

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 1.13.9 or later
Fixed in 1.13.9
Interim mitigation

Upgrade to version 1.13.9 or later. Review access controls and ensure all endpoints handling sensitive customer or order data properly authenticate and authorize requests.

Recommended fix High confidence

1.13.9

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Email Marketing for WooCommerce by Omnisend' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 1.13.9 from the WordPress plugin repository and upload it
  5. Verify the plugin version shows 1.13.9 after updating
  6. Test that the WooCommerce email marketing functionality continues to work correctly

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

Fix this in Email Marketing For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47244 — 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-2023-47244 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