CVE-2017-11347
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 · uneditedAuthenticated Code Execution Vulnerability in MetInfo 5.3.17 allows a remote authenticated attacker to generate a PHP script with the content of a malicious image, related to admin/include/common.inc.php and admin/app/physical/physical.php.
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 confidenceMetInfo 5.3.17 contains an authenticated code execution vulnerability where a remote authenticated attacker can upload or generate a PHP script containing malicious image content through admin/app/physical/physical.php, leading to arbitrary code execution on the server.
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.3.17CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 MetInfo installation and versionLocate the MetInfo installation directory and check the version file (typically version.php or similar in the root or includes directory) to confirm the exact installed version numberAffected if The installed version is exactly 5.3.17
-
Verify admin panel accessibilityCheck if the admin panel at /admin/ is accessible without additional authentication barriers beyond standard login, and determine if any user accounts have administrative privilegesAffected if Untrusted or compromised user accounts can access the admin panel with upload capabilities
-
Confirm physical.php exists and is accessibleVerify the presence of admin/app/physical/physical.php file in the web root and check if it is accessible to authenticated admin usersAffected if The file exists and is reachable by admin users through the web interface
-
Inspect upload directory configurationsCheck web server and application configuration for directories where uploaded files are stored, looking for any PHP execution permissionsAffected if Upload directories allow PHP execution or lack restrictions on file type extensions
-
Review recent file modifications in upload areasExamine upload directories for any recently created or modified PHP files that may contain image headers but actual PHP codeAffected if Unexpected PHP files are found in upload directories, especially those with double extensions like .php.jpg or image file signatures
You are affected if MetInfo version 5.3.17 is installed and the admin panel is accessible to untrusted users, allowing them to access admin/app/physical/physical.php for malicious file uploads.
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 admin panel access to trusted users only, implement strict input validation and sanitization on file upload functionality, disable PHP execution in upload directories, and upgrade to a patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11347 — 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-11347 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