Omnisend for WooCommerce <= 1.18.0 — Unauthenticated Omnisend Account Takeover via Predictable Connect Token
CVE-2026-42668Published · Updated Action summary
Affected: ≤1.18.0Update to 1.18.1 or newer
All remediation steps- Severity
- High7.5
- CVSS
- 7.5CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:HIntegrity- High
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
Email Marketing for WooCommerce by Omnisend omnisend-connect
- Affected≤ 1.18.0
- Patched in1.18.1
Update to 1.18.1 or newer.
You are affected if you run ≤ 1.18.0. Version 1.18.1 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Email Marketing for WooCommerce by Omnisend.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 1.18.1, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Email Marketing for WooCommerce by Omnisend to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to 0xzenko.
The Omnisend for WooCommerce plugin for WordPress is vulnerable to an unauthenticated account takeover via insufficiently random values in versions up to, and including, 1.18.0. This is due to the generate_install_url() function deriving the OAuth connect token solely from the Unix timestamp at page-load time (hash('sha256', time())), which yields only ~86,400 distinct values per day and is trivially brute-forceable. This makes it possible for unauthenticated attackers to predict the connect token, authenticate to the POST /wp-json/omnisend-api/v1/connect REST endpoint, and replace the store's omnisend_api_key and brand_id with attacker-supplied values, redirecting all customer PII synchronization, order webhooks, and marketing communications to the attacker's Omnisend account.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Email Marketing for WooCommerce by Omnisend
All 4| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Missing Authorization ≤1.19.0Update to 1.19.1 | CVE-2026-57632 | |
| Medium4.3 | Cross-Site Request Forgery ≤1.14.3Update to 1.14.4 | CVE-2024-32101 | |
| Medium5.3 | Sensitive Information Exposure ≤1.13.8Update to 1.13.9 | CVE-2023-47244 |
- Medium4.3Missing Authorization
≤1.19.0Update to 1.19.1
- Medium4.3Cross-Site Request Forgery
≤1.14.3Update to 1.14.4
- Medium5.3Sensitive Information Exposure
≤1.13.8Update to 1.13.9
Timeline
CVE published
Severity high, CVSS 7.5
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.
