# CVE-2026-109307: Craft CMS 5.0.0 before 5.10.14 DOM XSS via returnUrl in 2FA Verification

> Attackers can execute JavaScript in the authenticated control panel via DOM XSS in the 2FA verification flow, potentially taking over accounts.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-c72m-w87q-gvqm, GHSA-w5rh-mhxj-wr8r

## What is CVE-2026-109307?

CVE-2026-109307 is a low-severity cross-site scripting vulnerability in craftcms cms, published on 12 Oct 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

Craft CMS 5.0.0 before 5.10.14 contains a DOM-based cross-site scripting vulnerability in the control panel login and 2FA verification flow, where a user-controlled returnUrl accepting javascript: URLs is used in client-side navigation. Attackers can lure a 2FA-enabled victim into opening a crafted /admin/login?verify=1 URL between password submission and TOTP verification, executing JavaScript in the authenticated control panel with the victim's permissions.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-109307 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109307 is a low-severity cross-site scripting vulnerability in craftcms cms, published on 12 Oct 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-109307 in the wild and no public exploit code.

Affected product: craftcms cms. 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-109307/ (Markdown: https://insights.sbomify.com/CVE-2026-109307/index.md)
```

## Sources

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

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