CVE-2018-16763: Pre-Auth RCE in FUEL CMS 1.4.1
- Vendor
- Thedaylightstudio
CVE-2018-16763 is a pre-authentication remote code execution vulnerability in FUEL CMS 1.4.1. The flaw allows PHP code evaluation through unsanitized user-controlled input supplied to the pages/select/ filter parameter or the preview/ data parameter. Because attacker-supplied input is evaluated as PHP code, a remote unauthenticated attacker can execute arbitrary code on the underlying server in the context of the web application.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can result in full remote code execution on the affected FUEL CMS server without prior authentication. An attacker may execute arbitrary system commands via PHP, deploy web shells or additional malware, modify application content, access or alter data available to the CMS, and use the compromised host as a pivot for further intrusion activity.
Mitigation
If you can’t patch tonight, do this now.
Restrict public access to administrative and preview-related application functionality where feasible, place the CMS behind a reverse proxy or WAF with rules blocking exploitation attempts against the affected parameters, and reduce the impact of compromise by hardening the PHP runtime and web server account permissions. Network segmentation, least-privilege filesystem permissions, and disabling dangerous PHP execution pathways where operationally possible can further limit post-exploitation impact until remediation is completed.
Remediation
Patch, then assume compromise.
Upgrade FUEL CMS to a version that addresses CVE-2018-16763, if an official fixed release is available in the deployment’s support path. If upgrading is not immediately possible, modify the application code or apply a vendor-supported patch to prevent user-controlled input in the affected parameters from being evaluated as PHP code. Review the deployment for signs of compromise and remove any unauthorized code or persistence mechanisms after patching.
Exploits
17 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit; 3 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2018-16763 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2018-16763?
- Yes. Mallory tracks 17 public exploits or proofs of concept for CVE-2018-16763, the earliest disclosed Oct 10, 2020.
- Is there a patch for CVE-2018-16763?
- Upgrade FUEL CMS to a version that addresses CVE-2018-16763, if an official fixed release is available in the deployment’s support path. If upgrading is not immediately possible, modify the application code or apply a vendor-supported patch to prevent user-controlled input in the affected parameters from being evaluated as PHP code.
- What products are affected by CVE-2018-16763?
- Thedaylightstudio Fuel Cms.
- How severe is CVE-2018-16763?
- CVE-2018-16763 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 82.7% (100th percentile) as of Oct 16, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.