# CVE-2026-121472: AutomatorWP < 6.0.8 - Zoom/AWeber Integration Connection Hijack via CSRF

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

The AutomatorWP  WordPress plugin before 6.0.8 does not bind the requests that complete its Zoom and AWeber integration connections to the administrator who started them, allowing attackers to make a logged-in administrator replace the stored integration credentials with the attacker's own via a CSRF attack, diverting the data the site sends to those services into an account the attacker controls. Exploitation requires the integration to already be connected and knowledge of the site's OAuth client identifier.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / AutomatorWP: ≥ 0; < 6.0.8 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-352

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/b1746ba7-11a6-4946-8ed3-be19e570ad26/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/b1746ba7-11a6-4946-8ed3-be19e570ad26/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

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

Revision: 72b01720ea6f67e908667753ec13069e44fa9e75b42fcaf98e5e3f98bf01413c

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

## 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.