dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-41454

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 arbitrary file upload vulnerability in the UI login page logo upload function of Process Maker pm4core-docker 4.1.21-RC7 allows attackers to execute arbitrary code via uploading a crafted PHP or HTML 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

Arbitrary file upload vulnerability in Process Maker pm4core-docker 4.1.21-RC7 allows unauthenticated attackers to upload malicious PHP or HTML files through the UI login page logo upload function, enabling arbitrary code execution on the server.

MitigationImplement strict allowlist-based file type validation, store uploads outside the web root with randomized filenames, and disable script execution in the upload directory.

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

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

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 the installed Process Maker product
    Locate the application and confirm it is pm4core-docker (Process Maker). Check Docker container names, application headers, or product documentation.
    Affected if The system is not running pm4core-docker
  2. Check the installed version
    Run 'docker ps' to list containers, then inspect the container or check application files for version information. Compare against 4.1.21-RC7.
    Affected if The version is 4.1.21-RC7 or falls within the affected version range
  3. Verify the logo upload feature is accessible on the login page
    Navigate to the Process Maker login page and inspect whether a logo upload function is present in the UI or can be accessed via login page parameters.
    Affected if The logo upload functionality is enabled and accessible without authentication
  4. Check upload directory script execution settings
    Examine the web server configuration and upload directory for script execution permissions. Look for .htaccess, nginx config, or upload path settings.
    Affected if The upload directory allows execution of uploaded PHP or HTML files (no restrictions on script execution)

The environment is affected if running pm4core-docker version 4.1.21-RC7 with the logo upload feature accessible on the login page, as an unauthenticated attacker could upload and execute malicious files.

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

Implement strict allowlist-based file type validation, store uploads outside the web root with randomized filenames, and disable script execution in the upload directory.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41454 — 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-41454 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