External risk intelligence

Batflat CMS Contact Endpoint PHP Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-111559

The vulnerability exists in a CMS, which is typically deployed as a public-facing web application. The specific vulnerable endpoint is a contact form, a common feature exposed to the internet to facilitate communication from users or visitors, making it highly likely to be reachable from the public internet in standard deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory highlights a critical security flaw in Batflat CMS, a content management system, related to how it handles incoming messages through its contact form. The vulnerability allows unauthenticated remote attackers to execute arbitrary PHP code on affected systems, potentially leading to a compromise. The issue is significant because the software is no longer maintained, meaning there will be no official fix.

  • Unauthenticated attackers can run custom code.
  • Unpatched, unmaintained software poses ongoing risk.
  • Confirm relevance and assess exposure of Batflat CMS.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability by sending a specially crafted POST request to the `/contact` endpoint. This could lead to arbitrary PHP code execution on the server, with the privileges of the `www-data` user. Since the project is no longer maintained, there is no fix available.

  • No authentication required.
  • Triggered via POST request to contact endpoint.
  • Arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated remote attacker to execute arbitrary PHP code on the server with the privileges of the `www-data` user. This could occur when the unmaintained Batflat CMS is deployed and the contact endpoint is accessible. The project is no longer maintained, meaning this issue will likely remain unfixed.

  • Server-side code execution.
  • Crafted POST request to contact endpoint.
  • Compromise of the web server.

Operational Fix

Recommended remediation, mitigation, and detection steps

The unmaintained Batflat CMS has a critical vulnerability allowing unauthenticated remote code execution via the contact endpoint. Since the project is no longer maintained, there will be no official fix. Owners must first locate all instances of Batflat CMS, assess their exposure and business criticality, and then determine a remediation path, which may involve vendor coordination if a third party provides hosting or support, or planning for migration or containment.

  • Application owners must address this.
  • Verify public accessibility and criticality.
  • Plan for containment or migration.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Batflat CMS?

Batflat CMS is a lightweight content management system used to build and manage websites. It provides a platform for users to publish digital content and interact with visitors through features like contact forms. Because it is a web-based application, it typically runs on a server environment where it processes incoming web traffic to deliver pages and handle user input.

What does CWE-1336 mean for CVE-2026-111559?

CWE-1336 refers to the improper neutralization of special elements used in a template engine. In the context of this vulnerability, it means the software fails to properly clean or validate data submitted through its contact form. Because this input is not sanitized, an attacker can inject malicious PHP code that the server then processes and executes as if it were a legitimate part of the application.

How is the code execution vulnerability triggered?

The flaw is triggered when an attacker sends a specifically crafted POST request to the application's /contact endpoint. This vulnerability does not require the attacker to be logged in or have any special permissions. Simply navigating to the website and submitting a standard message through the contact form does not trigger the bug; it requires a malicious payload specifically designed to manipulate the underlying server-side code.

Is my Batflat CMS instance at risk?

If you are running Batflat CMS, you should assume risk. According to Halo Surface Signal, this vulnerability is particularly concerning because the software is designed as a public-facing web application. Since the vulnerable contact form is a standard feature typically exposed to the internet, any installation reachable by the public is likely to be accessible to external attackers.

What steps should I take if I use Batflat CMS?

Because this project is no longer maintained and will not receive an official security update, you should prioritize identifying where the software is deployed in your environment. Assess the business criticality of those instances and plan for migration to a supported platform. In the interim, consider restricting access to the application or disabling the vulnerable contact endpoint if possible to reduce the risk of compromise.