CVE
Batflat remote code execution via template injection in /contact
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts name no workaround. The affected feature is the public /contact form, and the facts do not say whether disabling or restricting that form is a supported measure.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- First public exploit on GitHub Nov 16
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 57/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Batflat CMS, from the vendor sruupl, has a flaw in its /contact endpoint where submitted data is not sanitized. A remote attacker can exploit it without logging in by sending a crafted POST request, which allows arbitrary PHP code to run with www-data user privileges. The project is no longer maintained and the issue has not been fixed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Batflat CMS does not sanitize data passed to the /contact endpoint. A remote unauthenticated attacker can send a POST request with a crafted message, causing arbitrary PHP code execution with www-data user privileges.
The project is no longer maintained and the issue has not been fixed.
Who should check
Anyone running sruupl Batflat CMS 1.2.0 through 1.3.6 with the public /contact form exposed; the project is unmaintained and unpatched.
“From 1.2.0 through 1.3.6”
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 62 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts name no workaround. The affected feature is the public /contact form, and the facts do not say whether disabling or restricting that form is a supported measure.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-111559 (Remote Code Execution in Batflat CMS), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-111559 (entry last updated 2026-11-16):
Affected:
- sruupl Batflat: from 1.2.0, through 1.3.7
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Batflat CMS versions 1.2.0 through 1.3.6 (per CERT Polska) (source: https://cert.pl/en/posts/2026/11/CVE-2026-111559/)
- The public /contact form is reachable and passes user input to the template engine (source: https://github.com/Tymbark7372/CVE-2026-111559)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-111559 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111559 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert.pl/en/posts/2026/11/CVE-2026-111559
- https://github.com/Tymbark7372/CVE-2026-111559
- https://cert.pl/en/posts/2026/11/CVE-2026-111559/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-111559
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-111559"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Exploit code on GitHub
Tymbark7372/CVE-2026-111559
Affected versions
- sruupl Batflat
From 1.2.0 · through 1.3.7
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Repository
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111559
Is CVE-2026-111559 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
What does this mean?
The public /contact form in Batflat CMS passes user input to the template engine without the handling the advisory describes, which lets an attacker cause arbitrary PHP code execution with www-data user privileges.Source: cert.pl, github.com
Which versions are affected by CVE-2026-111559?
Batflat: from 1.2.0 through 1.3.7.Source: cve.now feed data
Am I affected, and how do I check?
CERT Polska describes Batflat CMS versions 1.2.0 through 1.3.6 as affected, where the public /contact form is reachable and passes user input to the template engine. To check a installation, look at the installed Batflat version and whether the /contact form is present and reachable.Source: cert.pl, github.com
How do I fix CVE-2026-111559?
The checked facts do not list a fixed version or vendor patch identifiers, so no upgrade target can be named from them. Check the vendor's or CERT Polska's advisory for a fix before relying on any version.Source: cert.pl, github.com
What if there's no patch?
The checked facts name no workaround. The affected feature is the public /contact form, and the facts do not say whether disabling or restricting that form is a supported measure.Source: cert.pl, github.com