CVE-2026-123068 in Front User Submit Plugininfo

Summary

by MITRE • 11/22/2026

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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability identified in Front User Submit WordPress plugin versions prior to 5.1.0 represents a critical security flaw rooted in improper input validation during file upload operations. This specific issue is classified under CWE-434, which describes the unrestricted uploading of files with dangerous types. The core technical failure lies within an unauthenticated endpoint designed for user submissions, where the application fails to adequately inspect or sanitize the content of uploaded files before storing them on the server. By neglecting to enforce strict allowlists regarding file extensions or MIME type verification against actual file signatures, the system accepts arbitrary binary data without restriction. This lack of validation allows attackers to bypass standard security controls that typically prevent the storage of executable scripts within directories intended for static assets.

The operational impact is significantly amplified by how the server handles these uploaded files upon subsequent retrieval. Instead of serving them with a restrictive Content-Type header or forcing a download, the application derives the content type dynamically from the file's byte structure and serves it back to clients with an inline disposition. This configuration instructs web browsers to render the content directly within the current page context rather than prompting for a save action. Consequently, when an attacker uploads a crafted HTML or SVG payload containing malicious JavaScript code, the server stores this payload and later delivers it as executable script material. The combination of unrestricted upload capabilities and permissive serving headers creates a direct pathway for Cross-Site Scripting attacks, specifically stored XSS scenarios where the malicious content persists on the server until accessed by victims.

This vulnerability enables unauthenticated attackers to achieve arbitrary code execution within the context of any user who views the infected page. Because the script executes in the same origin as the WordPress site, it inherits all associated privileges and cookies. This is particularly dangerous for administrative users; if an administrator or any privileged account opens a URL pointing to the stored payload, the malicious JavaScript runs with full authority over that session. Attackers can leverage this access to hijack admin sessions, steal sensitive data such as database credentials or user information, deface the website, or install further malware and backdoors. The ability to obtain same-origin URLs ensures high reliability in exploitation, as modern browser security policies like Same-Origin Policy do not restrict execution of scripts loaded from the site's own domain.

Mitigation strategies must focus on immediate remediation through software updates and robust server-side configuration changes. Administrators should upgrade the Front User Submit plugin to version 5.1.0 or later, where these validation checks have presumably been implemented by the developers. In cases where upgrading is not immediately feasible, temporary mitigations include disabling file upload functionality for unauthenticated users if possible, or implementing a Web Application Firewall rule that blocks requests containing suspicious patterns in uploaded files. Additionally, server configuration should be reviewed to ensure that directories used for user uploads do not have execute permissions and are configured to serve all content with a Content-Disposition header set to attachment rather than inline. This forces browsers to download the file instead of rendering it, effectively neutralizing the XSS vector even if malicious payloads are successfully uploaded. Regular security audits and penetration testing should be conducted to verify that input validation mechanisms are functioning correctly across all public-facing endpoints.

Responsible

WPScan

Reservation

11/05/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

low

Sources

Do you know our Splunk app?

Download it now for free!