← All security briefings

Attention

ARForms 7.2.4 and earlier (CVE-2026-111190): unauthenticated arbitrary file upload through a public File field

Identifiers: CVE-2026-111190

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

ARForms versions up to 7.2.4 let an unauthenticated visitor submit a published public form containing a File field with a crafted filename or header that bypasses the upload checks, placing an executable PHP file in a public directory. Wordfence tracks this as CVE-2026-111190. Remote code execution is possible, subject to the server's execution configuration. ARForms Lite is a separate product and is not covered by this range.

Classification reason: Checked 11 November 2026. Wordfence published and updated the advisory on 10 November 2026, the disclosure date, and is the source for the CVE, affected range and fixed floor. The vendor changelog dates 7.3 to 7 November 2026 and describes only minor fixes, which corroborates the release and its date but not the specific CVE. The public CNA endpoint for CVE-2026-111190 returned no record during this check, so CNA corroboration is not asserted.

Impact

An attacker-chosen PHP file in a web-reachable directory is a direct path to site takeover wherever the server executes PHP from that location. Where execution is blocked, the file still represents an unwanted foothold that must be found and removed. No observed exploitation is established by the reviewed sources.

Who is affected

Sites running the ARForms plugin at 7.2.4 or earlier with at least one published, publicly accessible form that includes a File field.

Products and versions

Products and versionsAffectedFixed
ARForms <= 7.2.4 7.3

Exploitation evidence

Exploitation not established. No in-the-wild exploitation is established by Wordfence or the vendor as of 11 November 2026.

Sources: Wordfence Intelligence, ARForms

Actions

  1. Record the exact ARForms version and list every published form that contains a File field.
  2. Verify a restorable backup, update to 7.3 or later, then test submission, file storage and notification email with harmless data.
  3. Review public File fields and remove any that are not needed; moving a visible form elsewhere alone is not a proven mitigation for the upload endpoint.
  4. Investigate unexplained files in upload and public directories; preserve evidence and logs, then have your provider isolate or clean them up rather than leaving a possibly executable file reachable from the web.

Unknowns

  • Whether the vendor's 7.3 release, described only as minor fixes, was intended to address this specific CVE.
  • Which hosting execution configurations limit the impact of an uploaded PHP file.

Sources

  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/arforms/arforms-724-unauthenticated-arbitrary-file-upload-to-remote-code-execution-via-x-filename-header
  • ARForms · retrieved https://www.arformsplugin.com/documentation/changelog/

Change history

  1. — Published: Published 11 November 2026 following the Wordfence advisory of 10 November 2026; vendor release 7.3 dated 7 November 2026.

Subscribe: RSS feed · JSON Feed · Feed format and fields