Opens in a new tab
Published : November 15, 2026

CVE-2026-111190: ARForms <= 7.2.4 Unauthenticated Arbitrary File Upload to Remote Code Execution via X-FILENAME Header PoC, Patch Analysis & Rule

Plugin arforms
Severity High (CVSS 8.1)
CWE 434
Vulnerable Version 7.2.4
Patched Version —
Disclosed November 9, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-111190 (metadata-based): This is an unauthenticated arbitrary file upload vulnerability in the ARForms WordPress plugin, affecting all versions up to and including 7.2.4. The vulnerability resides in the plugin’s form file-upload handler, which takes the stored filename from an attacker-controlled request header (X-FILENAME) and fails to adequately restrict file types or contents. This allows an unauthenticated attacker to write a PHP file to a publicly accessible directory, leading to remote code execution. CVSS score is 8.1 (High), with a vector of CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating high confidentiality, integrity, and availability impact, though attack complexity is high, likely due to the requirement for a publicly accessible form with a File field.

Root Cause: The root cause is an unrestricted upload of a file with a dangerous type (CWE-434). Inferred from the CWE and description, the plugin’s upload handler likely fails to validate the file extension and MIME type against an allowlist, and instead relies on client-supplied data (the X-FILENAME header) to determine the stored filename. The handler may also perform insufficient content inspection, allowing PHP code to be embedded in an otherwise allowed file type (e.g., polyglot or double extension). These conclusions are inferred from the CWE and vulnerability description; no source code is available to confirm the exact implementation flaw.

Exploitation: An attacker would first identify a published form containing a File field. The form’s file-upload endpoint is likely a WordPress AJAX action (e.g., admin-ajax.php?action=arforms_upload) or a direct PHP file in the plugin directory. The attacker crafts a malicious file (e.g., a PHP shell) and submits it via a multipart/form-data POST request, setting the X-FILENAME header to a name with a .php extension (e.g., shell.php). If the plugin performs content checks, the attacker may use a double extension (e.g., shell.php.jpg) or embed PHP code within an image file (e.g., a GIF89a header followed by PHP code). The uploaded file is stored in a publicly accessible directory (e.g., wp-content/uploads/arforms/), and the attacker accesses it to execute arbitrary code. The exact endpoint and parameter names are not specified in the metadata, so the PoC assumes common WordPress AJAX patterns and uses the header name from the CVE title.

Remediation: The fix likely requires implementing a strict allowlist of permitted file extensions and MIME types, validating the file content to ensure it matches the expected type, and ignoring client-supplied filenames entirely in favor of server-generated safe names. The patched version 7.3 presumably addresses these issues by sanitizing the filename, enforcing proper file type checks, and possibly storing files outside the web root or with non-executable permissions.

Impact: Successful exploitation allows an unauthenticated attacker to execute arbitrary PHP code on the server, leading to full site compromise. The attacker could read sensitive data (e.g., wp-config.php), modify content, create administrative accounts, or use the server for further attacks. The high CVSS impact metrics reflect the severity of remote code execution.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-111190 (metadata-based)
# This rule blocks attempts to upload a PHP file via the ARForms file-upload handler
# by detecting the X-FILENAME header containing a .php extension. The exact AJAX
# action is not specified in the metadata, so the rule targets the header directly
# without URI restrictions, which may cause false positives if the header is used
# legitimately. Precision is limited by available information.

SecRule REQUEST_HEADERS:X-FILENAME "@rx .php($|?)" 
    "id:2026111190,phase:2,deny,status:403,msg:'CVE-2026-111190: ARForms arbitrary file upload attempt via X-FILENAME header',severity:'CRITICAL',tag:'CVE-2026-111190',tag:'CWE-434'"

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.