CVE-2026-7655
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 · uneditedThe SureCart plugin for WordPress is vulnerable to privilege escalation via account takeover in versions up to, and including, 4.2.3. This is due to the plugin not properly validating a user's identity prior to updating their details like email during customer profile synchronization from webhook events. This makes it possible for unauthenticated attackers to change linked user's email addresses, including administrators if the administrator account is linked to a SureCart customer record, and leverage that to reset the user's password and gain access to their account if the customer ID is known.
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 · high confidenceThe SureCart WordPress plugin (versions up to 4.2.3) lacks proper identity validation in its webhook handling for customer profile synchronization. Unauthenticated attackers can exploit this by sending crafted webhook requests with a known customer ID to modify the linked user's email address. If an administrator has a linked SureCart customer record, attackers can change the email and trigger a password reset to gain administrative access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed SureCart plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find SureCart, or check the version in the plugin's main file header. Alternatively, check the /wp-content/plugins/surecart/ directory or version file.Affected if Version is 4.2.3 or earlier (vulnerable). Version 4.2.4 or later is patched.
-
Verify webhook endpoint is accessibleCheck if the SureCart webhook endpoint responds. This is typically at /?surecart-webhook=1 or similar. Look for webhook configuration in SureCart settings under Webhooks or API settings.Affected if Webhook endpoint is publicly accessible without authentication (default vulnerable state).
-
Identify WordPress users linked to SureCart customer recordsCheck WordPress user meta or SureCart customer data to see which users have linked SureCart customer profiles. Look for users with 'surecart_customer_id' meta key or check in SureCart admin panel for linked accounts.Affected if Any WordPress administrator account has a linked SureCart customer record, as this enables the privilege escalation path.
-
Review recent email address changes on user accountsQuery WordPress user_meta for changes to user_email or billing_email fields. Check user edit history or audit logs for unexpected email modifications on administrator accounts.Affected if Any administrator account shows an email change that was not performed by a legitimate admin.
-
Check for unauthorized password reset requestsReview WordPress logs, email server logs, or SureCart activity logs for password reset emails sent to administrator accounts that were not requested by those users.Affected if Password reset emails were sent to admin accounts without corresponding legitimate reset requests.
-
Inspect webhook request logs for suspicious activityCheck server access logs or SureCart webhook logs for incoming POST requests to the webhook endpoint with customer_id parameters that may indicate enumeration or manipulation attempts.Affected if Webhook requests exist with customer IDs that correspond to administrator-linked customer records, especially from unfamiliar IP addresses.
A user is affected if they have SureCart plugin versions 4.2.3 or earlier installed with webhook functionality enabled AND any administrator account has a linked SureCart customer record, creating a path for unauthorized email changes and privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to SureCart version 4.2.4 or later which implements proper user identity validation before allowing email or profile updates via webhooks. Until patched, monitor for unauthorized email changes and consider unlinking high-privilege WordPress accounts from SureCart customer records.
4.2.4 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find SureCart in the plugin list
- If an update is available, click 'Update Now' to update to the latest version
- Verify the update completed successfully
- Ensure any administrator accounts linked to SureCart customer records are reviewed for suspicious activity
- Consider changing passwords for administrator accounts that may have been linked to SureCart customer records
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7655 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7655 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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