# CVE-2026-118167: MC4WP: Mailchimp for WordPress < 4.15.0 - Unauthenticated Subscription Audience Override

Status: published. Published: 2026-11-06. Updated: 2026-11-06.

The MC4WP: Mailchimp for WordPress plugin before 4.15.0 does not validate that the Mailchimp audience a sign-up form or bundled integration subscribes a visitor to matches the audience configured by the site owner, allowing unauthenticated visitors to subscribe arbitrary email addresses to any other audience in the site's connected Mailchimp account.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / MC4WP: Mailchimp for WordPress: ≥ 0; < 4.15.0 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-863

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/11752539-1dc8-4adb-a680-ce7ecaaff4d1/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/11752539-1dc8-4adb-a680-ce7ecaaff4d1/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-118167; retrieved 2026-11-06; source updated 2026-11-06

Revision: 9a154c1be81a871f82e2f0698c8828078e791cdb87032c151fe506514f533743

Canonical: https://y2.dev/cve/CVE-2026-118167

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.