The Front User Submit WordPress plugin before 5.1.0 does not validate the content of files uploaded through one of its
Source GCVE Database
Not known to be exploited : upgrade to 5.1.0 soon.
Data as of 22 Nov 2026, 07:27 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 5.1.0
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade Front User Submit (WordPress plugin) to 5.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Front User Submit | Affected
| Fixed in
|
AI-suggested
A fixed version 5.1.0 or later of the Front User Submit plugin should be applied to address this vulnerability. Since the input does not provide explicit patch information, users should upgrade to version 5.1.0 or later where this issue is resolved. Until then, restrict access to the upload endpoint or disable the plugin if possible.
Description
The Front User Submit WordPress plugin versions before 5.1.0 contain a vulnerability where files uploaded through an unauthenticated endpoint are not properly validated. These files are served back with a Content-Type based on their content and an inline disposition, enabling attackers to upload HTML or SVG files that execute arbitrary JavaScript in the browsers of users who open them, including administrators.