Introduction
When a Lucee Server comes up with no administrator password configured, its first-run setup pages hand the keys to whoever asks first. On vulnerable builds, an unauthenticated remote user can reach a New Password form, submit a password of their choosing, and walk away with administrative control of the instance. The Shadowserver Foundation first observed exploitation evidence against this condition on 2023-10-24.
Lucee is an open source CFML (ColdFusion Markup Language) application server, developed by the Lucee Association Switzerland, a nonprofit Swiss association. Its stated technical goal includes providing CFML functionality with fewer resources and better performance than alternatives, and member companies take part in project governance with one vote each. It is a runtime for CFML applications, which puts it in the same ecosystem niche as commercial ColdFusion servers.
Technical Information
CVE-2016-20105 is classified as CWE-1188, insecure default initialization of a resource. The root cause is in Lucee's first-run administrator password setup flow. On affected builds, when no administrator password has yet been configured, the administrator entry points at /lucee/admin/web.cfm and /lucee/admin/server.cfm render a New Password form rather than a login prompt. Because this form is reachable without any prior authentication, any remote user who reaches it before a legitimate operator can submit the form and set the initial administrator password.
The scope is worth stressing. NVD describes the consequence as seizure of server administrative control. The available sources do not establish that the flaw itself is arbitrary code execution, so do not infer that outcome from the administrative takeover description.
Lucee ships two separate administrator contexts: the Web Administrator and the Server Administrator. These map to the two paths above and are distinct contexts, so a given deployment may expose either or both.
The fix commit for LDEV-926 clarifies how Lucee determines whether a context has a password at all. It checks three attributes on the root element of the context's configuration document:
hspw: hashed and salted passwordpw: hashed password, no saltpassword: encrypted password
If all three are absent, the context has no password configured, which is precisely the state that exposes the setup form on vulnerable builds. On newer Lucee builds, the documentation notes that the password is stored as hspw and salt in .CFConfig.json, with LUCEE_ADMIN_PASSWORD and -Dlucee.admin.password serving as a fallback only when no hspw exists.
Attack flow
- The attacker identifies Lucee hosts, for example using the Shodan query
html:"Lucee"or the FOFA queryapp="Lucee-Engine". - The attacker sends an unauthenticated GET request to
/lucee/admin/web.cfmor/lucee/admin/server.cfm. - If the response is HTTP 200 and renders the New Password set-password form rather than a login prompt, no administrator password is set and the context is open to takeover.
- The attacker submits the form with an attacker-controlled password, establishing the initial administrator password and gaining full administrative control of that Lucee context.
Proof of Concept
A public, verified proof of concept exists in the form of ProjectDiscovery's Nuclei template lucee-unset-credentials.yaml, which is the exact PoC referenced by the NVD and VulnCheck advisory for this CVE. It is a non-destructive detection PoC: it issues unauthenticated GET requests to the two admin entry points and confirms the host is in the vulnerable state when the response returns HTTP 200 and the body contains both the Lucee string and the un-configured password form marker box">New Password</div>. The presence of this form, instead of a login prompt, means no administrator password is set and the server is open to unauthenticated password takeover.
id: lucee-unset-credentials info: name: Lucee - Unset Credentials author: jpg0mez severity: high description: | The Lucee admin panel has a first-time setup page which allows any user to set the administrator password. reference: - https://luceeserver.atlassian.net/browse/LDEV-926 - https://www.petefreitag.com/blog/lucee-admin-password-box/ classification: cwe-id: CWE-798 metadata: verified: true max-request: 2 shodan-query: "html:\"Lucee\"" fofa-query: "app=\"Lucee-Engine\"" tags: lucee,default-login,unauth,vuln http: - method: GET path: - "{{BaseURL}}/lucee/admin/web.cfm" - "{{BaseURL}}/lucee/admin/server.cfm" stop-at-first-match: true matchers-condition: and matchers: - type: word part: body words: - 'Lucee' - 'box">New Password</div>' condition: and - type: status status: - 200
Reproduction
Point Nuclei at a target with this template:
nuclei -u https://target -t http/vulnerabilities/other/lucee-unset-credentials.yaml
Alternatively, manually request https://<target>/lucee/admin/web.cfm or https://<target>/lucee/admin/server.cfm. A 200 response rendering the New Password set-password form, rather than requiring an existing credential, confirms the host is exploitable. From there, an attacker can submit the form to set an attacker-controlled admin password and gain full administrative control of the Lucee server.
Scope and limitation
The publicly available PoC is a detection and verification template. It demonstrates and confirms the vulnerable unauthenticated set-password state but does not itself automate submitting a new password to complete the takeover. Supporting context from Pete Freitag's blog and Lucee issue LDEV-926 documents the password-setup behavior and the fix: Lucee removed the ability to set the initial password through the web admin, requiring a password.txt file or CFConfig instead. The fix commit is referenced at 206cdab0a7c6.
Detection Methods
CVE-2016-20105 is a configuration flaw, not a memory corruption bug. Detection has two jobs: find instances that still serve the setup form, and check whether someone already used it.
1. Network scanning with the public Nuclei template
The CVE record and the VulnCheck advisory both point to ProjectDiscovery's lucee-unset-credentials template. It sends a GET to the two admin endpoints and reports a hit only when all of the following are true: the HTTP status is 200, the body contains Lucee, and the body contains the setup-form marker box">New Password</div>. Scanning stops at the first match.
http: - method: GET path: - "{{BaseURL}}/lucee/admin/web.cfm" - "{{BaseURL}}/lucee/admin/server.cfm" stop-at-first-match: true matchers-condition: and matchers: - type: word part: body words: - 'Lucee' - 'box">New Password</div>' condition: and - type: status status: - 200
The matcher looks for the password-creation form, not just the admin login page, so a normal login page on a server that already has a password will not trigger it and false positives should be rare. The template metadata also includes discovery queries for building a target list: Shodan html:"Lucee" and FOFA app="Lucee-Engine". Check both endpoints, because the Web Administrator and the Server Administrator are separate contexts.
2. Commercial DAST coverage
Tenable Web App Scanning plugin 115029, "Lucee Unset Credentials" (Critical, check-based, present in the basic, full, PCI, and scan templates), flags Lucee servers configured with no credentials. Invicti has an equivalent check called "Lucee Unset Admin Password", which flags an admin interface reachable without any password set. Both are exposure checks: a finding means the setup form is still there, not that someone already used it.
3. Telling fixed builds from vulnerable ones by the page they serve
The fix (commit 206cdab0, for LDEV-926) replaced the web form on fixed builds. When no password is set, fixed builds now show a notice that the initial password can no longer be set in the browser. Pete Freitag's write-up shows this as a "No Password Set Yet!" page that tells the admin to put a password.txt file under /lucee-server/context/. So a Lucee instance with no password falls into one of two cases:
- Vulnerable: the page shows a usable New Password input.
- Fixed but still unconfigured: the page shows the
password.txtinstructions instead.
This lets you sort scanner hits by priority and write your own checks if Nuclei is not an option.
4. Host-side configuration checks
Scanning only sees what is reachable over the network. On the host, you can check the stored password directly. As noted, the fix commit decides whether a context has a password by looking at three attributes on the root element of its configuration document: hspw, pw, and password. If all three are missing, the context has no password. On newer Lucee builds, the password is stored as hspw and salt in .CFConfig.json, with LUCEE_ADMIN_PASSWORD and -Dlucee.admin.password used only as a fallback when no hspw exists. Auditing server and web contexts for missing password attributes finds the same weakness from inside, including on hosts the scanners cannot reach.
5. Hunting for prior exploitation
No public Sigma, YARA, Snort, or Suricata rules or attacker IoCs were found for this CVE. Because exploitation has been seen in the wild, build hunts around the vulnerable workflow:
- In web server or reverse-proxy access logs, look for requests, especially form submissions, to
/lucee/admin/web.cfmor/lucee/admin/server.cfmfrom IP addresses outside your admin networks. - Compare the current config against your provisioning records. If an
hspw,pw, orpasswordvalue exists that your team did not set, or the admin password stopped working, assume an outsider set it. - Invicti's guidance also recommends watching access logs for suspicious authentication attempts against the admin panel after you set a password.
One limit applies to all of these methods: they show that an instance is or was exposed. Proving compromise still means checking the admin logs and configuration changes made after the password was set.
Affected Systems and Versions
- Lucee Server versions 5.0.0.0 up to, but not including, 5.3.4.46.
- Both the Web Administrator (
/lucee/admin/web.cfm) and the Server Administrator (/lucee/admin/server.cfm) contexts are affected when no password is configured. - Fixed in Lucee Server 5.3.4.46 and later, where the exposed web password-setup form was removed in favor of the
password.txtor CFConfig flow.
Severity
| Rating source and version | Score | Meaning |
|---|---|---|
| CVE record, CVSS 3.1 | 8.1 | High |
| VulnCheck CNA, CVSS 4.0 | 9.2 | Critical |
| NVD assessment, CVSS 4.0 | Not provided | NVD states its assessment is not yet available |
The 8.1 value is consistent with CVSS 3.1. Attribute the higher CVSS 4.0 figure to VulnCheck, not to an NVD scoring decision.
Vendor Security History
The Lucee GitHub security advisory index includes advisories published in 2021 and 2025, including entries labeled Critical and High. This confirms that the project publishes security advisories, but the index alone is not enough to judge the completeness of Lucee's historical security record or to compare it with other server projects.
References
- NVD: CVE-2016-20105
- CVE Record: CVE-2016-20105
- VulnCheck Advisory: Lucee Server 5.0.0.0 < 5.3.4.46 Unauthenticated Admin Password Setup
- VulnCheck Advisory (alternate URL)
- Lucee fix commit 206cdab0a7c6 (LDEV-926)
- GitHub API view of commit 206cdab0a7c6
- LDEV-926: Stop allowing unauthenticated people set default passwords for web admins
- ProjectDiscovery Nuclei template: lucee-unset-credentials.yaml
- Nuclei template raw source
- Pete Freitag: Setting Lucee Admin Password with CommandBox
- Tenable WAS Plugin 115029: Lucee Unset Credentials
- Invicti: Lucee Unset Admin Password
- Lucee Security page
- Lucee About page
- Lucee GitHub Security Advisories
- Lucee configuration precedence documentation



