CVE-2026-15000
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 Connect Contact Form 7 and Mailchimp plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Mailchimp Merge Field Values in all versions up to, and including, 0.9.78.06 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is only triggered when a privileged user (Administrator) performs a Contact Lookup for the email address submitted via the CF7 form, meaning execution is deferred until an administrator interacts with the affected entry.
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 confidenceThis is a stored XSS vulnerability in the Connect Contact Form 7 and Mailchimp WordPress plugin. Unauthenticated attackers can inject malicious scripts through Contact Form 7 form submissions via Mailchimp merge fields. The payload is stored in the database and executes only when an Administrator accesses the Contact Lookup feature to view the submitted contact data, making it a deferred execution stored XSS.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedNavigate to WordPress admin > Plugins and look for 'Connect Contact Form 7 and Mailchimp' or check the wp-content/plugins directory for a plugin folder related to Contact Form 7 and Mailchimp integrationAffected if The plugin is installed and active
-
Check the installed plugin versionIn WordPress admin > Plugins, click on the plugin to view details and note the installed version number. Compare against the fixed version once releasedAffected if The installed version is older than the patched version (once available)
-
Verify Mailchimp API integration is configuredGo to the plugin settings page and check if a Mailchimp API key is saved and a Mailchimp list/audience is selectedAffected if Mailchimp integration is configured and active
-
Check if Contact Form 7 forms are connected to MailchimpIn the plugin settings or Contact Form 7 form编辑页面, verify that Mailchimp merge fields are mapped or that the form is set to send data to MailchimpAffected if Contact Form 7 forms are configured to sync with Mailchimp merge fields
-
Inspect the database for suspicious stored dataCheck the WordPress database tables where contact submissions are stored (typically created by the plugin) for unexpected script tags or HTML in merge field valuesAffected if Malicious script tags are present in stored contact/submission data
A user is affected if the Connect Contact Form 7 and Mailchimp plugin is installed with an unpatched version, Mailchimp integration is active, and Contact Form 7 forms are configured to sync with Mailchimp, allowing stored XSS to persist in the database.
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.
From vendor dataUpdate the plugin to the latest version once available, or implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_attr) and output escaping (esc_html, esc_attr) when displaying merge field values in the Contact Lookup admin interface.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15000 — 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-15000 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