dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-34074

CRITICAL · 9.4 CVSS v4.0 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An authenticated remote code execution vulnerability exists in Lucee’s administrative interface due to insecure design in the scheduled task functionality. An administrator with access to /lucee/admin/web.cfm can configure a scheduled job to retrieve a remote .cfm file from an attacker-controlled server, which is written to the Lucee webroot and executed with the privileges of the Lucee service account. Because Lucee does not enforce integrity checks, path restrictions, or execution controls for scheduled task fetches, this feature can be abused to achieve arbitrary code execution. This issue is distinct from CVE-2024-55354.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An authenticated RCE vulnerability exists in Lucee's admin interface (web.cfm) where the scheduled task functionality allows administrators to configure jobs that fetch remote .cfm files. These files are written to the webroot and executed with Lucee service account privileges. The feature lacks integrity verification, path restrictions, or execution controls.

MitigationRestrict administrative access to Lucee's admin interface via network segmentation or authentication, disable the scheduled task remote fetch feature if not needed, and apply vendor patches when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Lucee installation and version
    Locate Lucee installation and identify version. Check for lucee-server.xml or admin/configuration files, or query the admin API endpoint (e.g., /lucee/admin/web.cfm or /lucee/admin/server.cfm) for version information.
    Affected if Running an unpatched Lucee version where the scheduled task feature allows remote .cfm file fetching without restrictions.
  2. Confirm administrative access to Lucee admin interface
    Determine if the Lucee admin web.cfm or server.cfm endpoints are accessible. Check network accessibility and whether authentication is required/enforced. Inspect server configuration for admin password requirements.
    Affected if The Lucee admin interface (web.cfm) is accessible without proper authentication or network restrictions.
  3. Identify scheduled task configuration
    Navigate to the scheduled task section within the Lucee admin interface (typically under Services > Scheduled Tasks) or inspect the scheduled-tasks.xml configuration file in the Lucee server or web context directory.
    Affected if Remote URL scheduling is enabled and the feature allows fetching and executing remote .cfm files.
  4. Check webroot write permissions
    Verify that the Lucee service account has write access to the webroot directory where scheduled task files would be written. Inspect file system permissions on the web document root.
    Affected if The Lucee process can write files to the webroot, allowing remote payloads to be placed in an executable location.
  5. Review scheduled task execution settings
    Inspect the scheduled task configuration for options that allow 'url' or 'http' sources for task definitions. Check if there are any path restrictions or execution controls enabled.
    Affected if Remote URL-based task sources are permitted without integrity verification or path sandboxing.

A user is affected if they have Lucee installed with an accessible admin interface where the scheduled task feature permits fetching remote .cfm files and writing them to the webroot, combined with insufficient access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict administrative access to Lucee's admin interface via network segmentation or authentication, disable the scheduled task remote fetch feature if not needed, and apply vendor patches when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34074 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data