dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-35527

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-25
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 No privileges 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 arbitrary file upload vulnerability in /fileupload/upload.cfm in Daemon PTY Limited FarCry Core framework before 7.2.14 allows attackers to execute arbitrary code via uploading a crafted .cfm file.

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

The FarCry Core framework before version 7.2.14 contains an arbitrary file upload vulnerability in the /fileupload/upload.cfm endpoint. Attackers can upload malicious .cfm (ColdFusion Markup) files that get executed by the server, allowing remote code execution.

MitigationUpgrade to FarCry Core framework version 7.2.14 or later. Implement strict file type validation and content inspection for all upload endpoints, restricting uploads to only expected file types and storing files outside web-accessible directories.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify FarCry Core installation
    Locate the FarCry Core framework installation directory on your server. Common locations include the web root or application directories. Look for the core directory containing FarCry configuration files.
    Affected if FarCry Core framework is installed on the server
  2. Check FarCry Core version
    Examine the version information for the FarCry Core installation. Look for a version file, package.json, or Application.cfc that contains the version number. Compare the installed version against 7.2.14.
    Affected if The installed version is before 7.2.14 (e.g., 7.2.13, 7.2.0, older)
  3. Verify upload endpoint exists
    Check if the /fileupload/upload.cfm endpoint is present in the web-accessible directory. This file should exist in the deployed application structure.
    Affected if The /fileupload/upload.cfm file exists in the deployed application
  4. Check upload configuration
    Review the file upload configuration or the upload.cfm handler to determine if file upload functionality is enabled and what file types are accepted.
    Affected if File uploads are enabled and .cfm files are accepted without strict validation
  5. Verify uploaded files location
    Determine where uploaded files are stored. Check if uploaded files are placed in web-accessible directories where they could be executed by the ColdFusion server.
    Affected if Uploaded files are stored in web-accessible directories

You are affected if FarCry Core version is before 7.2.14 AND the /fileupload/upload.cfm endpoint exists with upload functionality enabled that permits .cfm file uploads to web-accessible locations.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FarCry Core framework version 7.2.14 or later. Implement strict file type validation and content inspection for all upload endpoints, restricting uploads to only expected file types and storing files outside web-accessible directories.

Recommended fix Moderate confidence

FarCry Core framework 7.2.14

  1. Verify current FarCry Core framework version by checking application configuration or version file
  2. Review FarCry Core 7.2.14 release notes for any required migration steps or breaking changes
  3. Backup the current FarCry Core application and database before upgrading
  4. Download FarCry Core framework version 7.2.14 from the official Daemon PTY Limited repository
  5. Replace existing framework files with version 7.2.14 files, preserving custom configurations
  6. Clear any compiled cached files in the application
  7. Test the upgraded application to verify functionality and that the file upload endpoint now properly validates file types
  8. Verify that .cfm files are no longer accepted by the /fileupload/upload.cfm endpoint
Caveat Review 7.2.14 release notes for any breaking changes or required configuration updates before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

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-2024-35527 — 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-2024-35527 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