Skip to main content
Menu
CVEs

Front User Submit stored XSS in file uploads

CVE-2026-123068Published , updated

Exploited
No known exploitation
Fix
Fixed in 5.1.0
Who is exposed
Not reported

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

Original 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

Upgrade to a fixed version: 5.1.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Affected versions

cve.now Index

0Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 55 if added to CISA KEV
  • Would score about 50 if CISA's SSVC rates exploitation active
  • Would score about 22 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-123068
RecordNVD · CVE-2026-123068
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploitwpscan.com · vulnerability/59235295-8a3f-498e-96ad-6ce01b4a485a

Questions about CVE-2026-123068

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: cve.now feed data

Which versions are affected by CVE-2026-123068?

Front User Submit: before 5.1.0.

Source: cve.now feed data

How do I fix CVE-2026-123068?

Upgrade to a fixed version: 5.1.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.