CVE-2024-11138
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 · uneditedA vulnerability classified as problematic has been found in DedeCMS 5.7.116. This affects an unknown part of the file /dede/uploads/dede/friendlink_add.php. The manipulation of the argument logoimg leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
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 confidenceDedeCMS 5.7.116 contains an unrestricted file upload vulnerability in /dede/friendlink_add.php. The 'logoimg' parameter accepts file uploads without proper validation, allowing remote attackers to upload arbitrary executable files (e.g., PHP webshells) to the web server. This leads to 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.116CVSS 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 versionLocate the DedeCMS installation and check the version number (typically found in version files, admin panel, or changelog). Compare your installed version to the affected version 5.7.116.Affected if The installed version is exactly 5.7.116.
-
Verify vulnerable file existsCheck if the file /dede/friendlink_add.php exists in the web root. This is the path referenced in the CVE as the location of the vulnerability.Affected if The file /dede/friendlink_add.php exists on the server.
-
Check admin directory accessibilityVerify that the /dede/ administrative directory is accessible from the web. Attempt to access the directory or the specific file via HTTP/HTTPS to confirm it responds.Affected if The /dede/ directory and friendlink_add.php are accessible via web request.
-
Confirm friendlink module is enabledCheck whether the friendlink (friendship link) feature is enabled in the DedeCMS admin panel. Look for friendlink management settings or related modules.Affected if The friendlink functionality is enabled and accessible without additional authentication barriers.
-
Inspect webroot for unexpected filesSearch the web-accessible directories for newly created PHP files with suspicious names (e.g., shell, cmd, exec, random strings). Check directories where uploaded files would be stored.Affected if Unknown or suspicious PHP files exist in the web root or upload directories.
You are affected if DedeCMS version 5.7.116 is installed, the /dede/friendlink_add.php file exists and is web-accessible, and the friendlink upload feature is enabled.
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 dataDisable the friendlink_add.php functionality until a patch is available; if required, implement strict allowlist-based file validation (verify MIME type, file extension, and file content), store uploads outside the webroot, and rename uploaded files.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11138 — 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-11138 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