CVE-2017-11756
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 · uneditedIn Earcms Ear Music through 4.1 build 20170710, remote authenticated users can execute arbitrary PHP code by changing the allowable music-upload extensions to include .php in addition to .mp3 and .m4a in admin.php?iframe=config_upload, and then using user.php/music/add/ to upload the code.
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 confidenceEarcms Ear Music allows remote authenticated users to execute arbitrary PHP code by modifying upload configuration to permit .php file extensions, then uploading malicious PHP files through the music upload functionality. This combines insecure direct object reference with unrestricted file upload of executable content.
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<= 4.1CVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:L/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 Earcms installation and versionLocate the Earcms Ear Music installation on the server and determine the exact version number by inspecting the software's version file, admin panel, or footer/header metadata. Compare your version against the affected range: any version <= 4.1 is within the vulnerable range.Affected if Your installed Earcms Ear Music version is 4.1 or lower.
-
Verify authenticated access to upload functionalityConfirm that the music upload feature is accessible to authenticated users (not only administrators). Check user role permissions or test with a standard user account to see if the upload interface is available.Affected if Authenticated users can access and use the music upload feature.
-
Inspect upload configuration for allowed extensionsLocate the upload configuration file or settings panel in Earcms. Examine the list of permitted file extensions for uploads. Look specifically for whether .php or other executable extensions are explicitly allowed in the configuration.Affected if The upload configuration permits .php file extensions (or permits any executable server-side script extensions).
-
Determine upload directory locationCheck where uploaded files are stored relative to the web root. Inspect the upload path configuration or examine actual uploaded files on the server to see if they reside within the publicly accessible web directory.Affected if Uploaded files are stored inside the webroot (web-accessible directory) rather than outside it.
You are affected if you are running Earcms Ear Music version 4.1 or lower AND the upload configuration allows .php extensions AND uploaded files are accessible via the web server.
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 file upload extensions to non-executable types (e.g., only .mp3, .m4a, .wav) and validate actual file content/MIME type server-side rather than trusting client-provided extension lists. Store uploaded files outside the webroot or rename them to prevent execution.
- 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-2017-11756 — 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-2017-11756 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