dbcve.org
InjectionWeakness · CWE-74

CVE-2024-52004

HIGH · 8.7 CVSS v4.0 Published 2024-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/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
MediaCMS is an open source video and media CMS, written in Python/Django and React, featuring a REST API. MediaCMS has been prone to vulnerabilities that upon special cases can lead to remote code execution. All versions before v4.1.0 are susceptible, and users are highly recommended to upgrade. The vulnerabilities are related with insufficient input validation while uploading media content. The condition to exploit the vulnerability is that the portal allows users to upload content. This issue has been patched in version 4.1.0. There are no known workarounds for this vulnerability.

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

MediaCMS versions before v4.1.0 contain an RCE vulnerability stemming from insufficient input validation during media file uploads. An attacker with upload privileges can upload specially crafted media files that allow arbitrary code execution on the server. The vulnerability is specific to installations where user content uploads are enabled.

MitigationUpgrade MediaCMS to v4.1.0 or later. There are no available workarounds; the only remediation is applying the patched version.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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. Identify MediaCMS version
    Locate the MediaCMS installation and check the version file or admin panel for the installed version number
    Affected if The installed version is before v4.1.0 (e.g., v4.0.x, v3.x, etc.)
  2. Verify if user content uploads are enabled
    Access the MediaCMS admin settings and check whether the option to allow user uploads is turned on; this is typically found under Content Settings or Upload Settings
    Affected if User content uploads are enabled in the MediaCMS configuration
  3. Confirm upload privilege settings
    Check the user roles and permissions configuration to see which user roles have the ability to upload media files
    Affected if Regular users or unauthenticated users have upload privileges granted
  4. Inspect upload file handling configuration
    Review the MediaCMS media upload settings to see what file types are permitted and whether any validation or sanitization is configured
    Affected if The system accepts media file uploads without strict file type restrictions or validation

You are affected if MediaCMS is installed with a version lower than v4.1.0 AND user content uploads are enabled, allowing authenticated users to upload media 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.

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

Upgrade MediaCMS to v4.1.0 or later. There are no available workarounds; the only remediation is applying the patched version.

Recommended fix High confidence

v4.1.0

  1. 1. Back up your current MediaCMS installation including database and uploaded media files
  2. 2. Navigate to your MediaCMS installation directory
  3. 3. If using git, pull the latest release: git fetch --all && git checkout tags/v4.1.0 -b upgrade-v4.1.0
  4. 4. If using pip, upgrade: pip install --upgrade mediamanager (or check for mediamcms package)
  5. 5. Run database migrations: python manage.py migrate
  6. 6. Collect static files if needed: python manage.py collectstatic --noinput
  7. 7. Restart the application services (Gunicorn, Celery, Nginx)
  8. 8. Verify the upgrade by checking the version in the admin panel or via: python manage.py show_version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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