CVE-2011-5134
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 · uneditedUnrestricted file upload vulnerability in editor/extensions/browser/file.php in the JCE component before 2.0.18 for Joomla! allows remote authenticated users with the author privileges to execute arbitrary PHP code by uploading a file with a double extension, as demonstrated by .php.gif. NOTE: some of these details are obtained from third party information.
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 confidenceUnrestricted file upload vulnerability in JCE component for Joomla! allows authenticated users with author privileges to upload files with double extensions (e.g., .php.gif), bypassing filename validation and enabling arbitrary PHP 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<= 2.0.17= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.0.10CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
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.
-
Verify JCE component is installedLog into Joomla administrator panel, navigate to Extensions > Manage (or Extensions > Extension Manager), and search for 'JCE' or 'com_jce' in the installed extensions listAffected if JCE component is found installed on the Joomla site
-
Identify installed JCE versionIn Joomla admin, go to Components > JCE Admin (or similar JCE management page) and locate the version number displayed; alternatively, check the version in the #__extensions database table for com_jceAffected if Version is 2.0.17 or lower, or matches 2.0.0 through 2.0.10 exactly
-
Confirm author-level user access existsNavigate to Users > Access Levels (or Users > Manage) in Joomla admin and check if any user groups with Author privileges exist and are assigned to active usersAffected if Author-level users or groups with upload permissions are present in the system
-
Inspect for double-extension filesUse file system search (find /path/to/joomla -name '*.php.*' -o -name '*.jpg.php' -o -name '*.gif.php') or check the Joomla media directory (typically /images/ or /media/) for files with double extensions that may contain PHP codeAffected if Any .php.gif, .php.jpg, or similarly named files are found in uploaded directories
If JCE component version 2.0.17 or below (including 2.0.0-2.0.10) is installed and author-level users with upload access exist, the environment is likely affected by this file upload vulnerability.
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 dataUpgrade JCE component to version 2.0.18 or later. Review server for any uploaded malicious files and implement server-side file type validation in addition to client-side checks.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-5134 — 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-2011-5134 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