# CVE-2026-9734: W3SC Elementor to Zoho CRM <= 2.2.0 - Cross-Site Request Forgery to Settings Update

> Attackers can trick admins into modifying Zoho CRM integration settings via CSRF, potentially hijacking credentials and data flow.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-qx49-qxg3-x53g

## What is CVE-2026-9734?

CVE-2026-9734 is a medium-severity vulnerability in w3scloud W3SC Elementor to Zoho CRM, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The W3SC Elementor to Zoho CRM plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.0. This is due to missing or incorrect nonce validation on the storeInfo function. This makes it possible for unauthenticated attackers to modify the plugin's Zoho CRM integration settings, replacing the configured data center, client ID, client secret, and user email credentials with attacker-controlled values via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-9734?


## How do I fix CVE-2026-9734?

No fix has been published for CVE-2026-9734 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9734 being exploited?

There is no known exploitation of CVE-2026-9734 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9734 and fix it if it is affected.

What it is: CVE-2026-9734 is a medium-severity vulnerability in w3scloud W3SC Elementor to Zoho CRM, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-9734 in the wild and no public exploit code.

Affected product: w3scloud W3SC Elementor to Zoho CRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9734/ (Markdown: https://insights.sbomify.com/CVE-2026-9734/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9734
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9734
- OSV: https://osv.dev/vulnerability/CVE-2026-9734

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9734/
Summaries are generated and may contain mistakes; the official description above is the record.