CVE-2024-35375
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 · uneditedThere is an arbitrary file upload vulnerability on the media add .php page in the backend of the website in version 5.7.114 of DedeCMS
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 · moderate confidenceAn arbitrary file upload vulnerability exists in the media add .php page in the backend of DedeCMS version 5.7.114, allowing authenticated attackers to upload malicious files to the server. The lack of proper file validation on this upload endpoint enables remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.7.114CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify DedeCMS installationLook for DedeCMS characteristic files such as /include/common.inc.php, /dede/login.php (backend), or check page footers for 'DedeCms' branding.Affected if The system is running DedeCMS
-
Verify DedeCMS versionCheck the version file (typically /include/common.inc.php or /data/admin/ver.txt) or access the backend login page which often displays the version.Affected if The installed version is exactly 5.7.114
-
Confirm backend access existsCheck if the backend directory /dede/ is accessible and whether default admin credentials are in use or if weak credentials are configured.Affected if The backend is accessible with valid credentials (required for exploitation)
-
Locate media upload endpointNavigate to the media management section in the backend, typically found under 'media' or 'files' in the navigation menu, accessing the file that handles uploads (often named media_add.php or similar).Affected if The media add functionality is present and accessible
-
Inspect file validation logicExamine the upload handler script source code in the media add page for proper file type checking, content validation, and file extension filtering.Affected if File validation is missing, weak, or can be bypassed (allows uploading of executable file types like .php)
The environment is affected if DedeCMS version 5.7.114 is running, the backend is accessible, and the media upload endpoint lacks proper file validation.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict backend administrative access, implement strict file type validation and content inspection on upload functionality, and apply vendor patches when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-35375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35375 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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