jDownloads 4.1.8 is a security update for Joomla sites that addresses five vulnerabilities affecting versions 1.0.0 through 4.1.7, including a critical remote code execution flaw requiring frontend upload permission. Site owners should update to 4.1.8 or later promptly, restrict frontend uploads until patching is complete, and distinguish these issues from a separate unauthenticated upload RCE that was fixed earlier in version 4.1.6.
Administrators using jDownloads should treat version 4.1.8 as a priority security update. The release resolves five CVEs affecting jDownloads 1.0.0 through 4.1.7, including a CVSS 4.0 10.0 remote code execution vulnerability. The critical issue fixed in 4.1.8 requires a user with frontend upload permission; it is not the separate unauthenticated upload vulnerability that affected jDownloads 4.1.0 through 4.1.5 and was fixed in 4.1.6.
What the jDownloads 4.1.8 Security Update Fixes
The jDownloads project identifies 4.1.8 as a security update. It addresses five vulnerabilities tracked in CVE records, all of which affect jDownloads versions 1.0.0 through 4.1.7. Updating to 4.1.8 or later is the documented remediation for this group.
The issues cover file-upload handling, server-side requests, download access controls, frontend publication workflow controls, and file-path handling. This breadth matters for sites that use jDownloads for member downloads, private documents, external download URLs, or frontend file submissions. A site can have exposure even when it does not use every jDownloads feature, so the installed version should be checked rather than assuming a particular configuration is unaffected.
The most serious issue in the 4.1.8 release is CVE-2026-117551, a critical remote code execution (RCE) vulnerability. The CVE record describes insufficient validation of frontend thumbnail uploads before version 4.1.8. A user who has frontend upload permission could upload executable content as a thumbnail and achieve PHP code execution on the server.
That permission requirement is a significant technical qualification, but it does not reduce the need to patch. Multi-user sites, public-facing submission workflows, sites with delegated content teams, and sites where upload permissions may have been granted too broadly should assess the issue urgently. Until the update is installed, disable frontend uploads where practical or limit them to the smallest necessary group of trusted users.
Verified jDownloads Vulnerabilities and Affected Versions
The table below summarises the verified CVEs relevant to this update history. Scores are CVSS 4.0 scores from the CVE records; they are not CVSS 3.1 scores. The five newer CVEs are fixed in 4.1.8. The older unauthenticated upload RCE is included because administrators need to verify that previously vulnerable 4.1.x installations have passed both patch milestones.
| Issue | CVE | Authentication | Affected versions | Recommended version | CVSS 4.0 | CISA KEV |
|---|---|---|---|---|---|---|
| RCE through frontend thumbnail upload | CVE-2026-117551 | User with upload permission | 1.0.0–4.1.7 | 4.1.8 or later | 10.0 Critical | Not listed |
| Server-side request forgery | CVE-2026-117543 | Authenticated | 1.0.0–4.1.7 | 4.1.8 or later | 8.9 High | Not listed |
| Download access-control flaw / IDOR | CVE-2026-117544 | None | 1.0.0–4.1.7 | 4.1.8 or later | 8.2 High | Not listed |
| Frontend publication workflow flaw | CVE-2026-117550 | Authenticated | 1.0.0–4.1.7 | 4.1.8 or later | 7.1 High | Not listed |
| Path traversal | CVE-2026-117542 | Authenticated | 1.0.0–4.1.7 | 4.1.8 or later | 5.1 Medium | Not listed |
| Unauthenticated arbitrary file upload / RCE | CVE-2026-61900 | None | 4.1.0–4.1.5 | 4.1.6 or later, then 4.1.8 or later | 10.0 Critical | Not listed |
CVE-2026-117543 concerns server-side request forgery (SSRF) in external download URL handling. In affected versions, redirect handling can allow the Joomla server to request internal or otherwise restricted resources and disclose responses. Sites using external download URLs should therefore review that configuration and inspect server logs for unexpected outbound requests.
CVE-2026-117544 is an access-control issue affecting downloads. It can allow files associated with other downloads to be retrieved without fully enforcing the target download's access rules. This creates a potential confidentiality concern for organisations using jDownloads to distribute restricted documents, customer files, partner resources, or member-only material.
CVE-2026-117550 affects frontend submission handling. It can bypass intended publication and ownership controls, potentially allowing unreviewed files to become published or ownership to be assigned contrary to policy. CVE-2026-117542 is an authenticated path traversal issue that can allow files to be moved or assigned outside the intended directory, potentially exposing file contents or removing source files from their expected locations.
Do Not Conflate the Two Critical RCE Issues
There are two distinct critical file-upload-related vulnerabilities in the verified record, and the fixed versions are different.
- CVE-2026-61900 affected jDownloads 4.1.0 through 4.1.5. It was an unauthenticated arbitrary file upload issue leading to remote code execution. It was fixed in version 4.1.6.
- CVE-2026-117551 affects jDownloads 1.0.0 through 4.1.7. It requires a user with frontend upload permission and was fixed in version 4.1.8.
For a site currently on 4.1.0 through 4.1.5, moving only to 4.1.6 would remove the earlier unauthenticated upload endpoint but would not address the five newer vulnerabilities fixed in 4.1.8. The practical destination is therefore jDownloads 4.1.8 or later. A historical review is also warranted when a site previously ran 4.1.0 through 4.1.5, because that earlier exposure was unauthenticated.
Conversely, administrators should not describe CVE-2026-117551 as unauthenticated. Accurate security communication helps teams prioritise correctly: its risk is tied to accounts and roles that have frontend upload capability, so reviewing those permissions is an immediate compensating control while the update is being scheduled.
Priority Actions for Joomla Administrators
Apply the update through a controlled maintenance process, but do not defer it unnecessarily. The following checklist is designed for site owners, freelance administrators, and agencies responsible for multiple Joomla installations.
- Inventory every site using jDownloads. Identify the installed version and whether the extension is active on public, staging, archived, or client-managed sites. Do not rely only on a central update dashboard if sites are administered separately.
- Prioritise versions 4.1.0–4.1.5. These versions were affected by CVE-2026-61900. Update through version 4.1.6 or later to remove that earlier unauthenticated upload issue, then install 4.1.8 or later to address the five CVEs covered by the current security release.
- Update all versions from 1.0.0 through 4.1.7. The five CVEs fixed by 4.1.8 affect this full range. Take a tested backup first, confirm that the backup can be restored, and record the installed extension version before and after maintenance.
- Restrict frontend upload permissions before patching. Temporarily disable frontend uploads if the business workflow permits. Otherwise, remove upload rights from unnecessary groups and confirm that only trusted users retain the capability.
- Review high-risk jDownloads features. Check external download URL settings, download access levels, frontend submission moderation, publication rules, and file ownership controls. The goal is to ensure that the patched configuration matches the site's intended content and access policy.
- Validate the result after the update. Confirm that jDownloads reports version 4.1.8 or later, test ordinary download and authorised upload workflows, and make sure access restrictions and moderation behaviour remain correct.
Agencies should communicate the distinction between the two RCE issues to clients. A concise change record should state whether a site was ever on 4.1.0–4.1.5, when it reached at least 4.1.6, and when it reached 4.1.8 or later. That history is useful when deciding the scope of a follow-up security review.
Post-Update Review and Defensive Monitoring
Patching removes the known vulnerable behaviour in the documented versions, but it does not by itself answer whether an older deployment was misused before the update. The appropriate review should be proportionate to the site's exposure, particularly for sites that accepted public submissions or ran a vulnerable 4.1.0–4.1.5 release.
Review relevant activity
Review Joomla, web server, and hosting logs for unusual file-upload events, unexpected file execution activity, abnormal download patterns, unexpected file moves, and unusual outbound requests from the Joomla host. The relevant indicators differ by issue: upload activity is particularly relevant to the two RCE CVEs, download activity is relevant to the access-control flaw, and outbound request activity is relevant to the SSRF issue.
Also review recent frontend submissions, publication status changes, and ownership assignments. Look for files that were published without expected moderation or that appear under an unexpected owner. For sites that distribute restricted information, review download access levels and investigate reports of files being available to users outside their intended access groups.
Strengthen the surrounding controls
Use least privilege for Joomla user groups and jDownloads permissions. Frontend upload rights should be granted only where there is a defined business need, and submission workflows should retain meaningful human review where public or semi-trusted users can contribute files. Keep backups current and make recovery testing part of the maintenance process rather than assuming that a backup is usable.
For sites that previously ran jDownloads 4.1.0 through 4.1.5, consider a focused post-update security audit. The purpose is not to assume compromise; it is to establish whether there is evidence of unexpected uploads or modifications from the period in which the unauthenticated issue was present.
How to Interpret CVSS, NVD Status, and CISA KEV
The CVSS values in this article are the CVSS 4.0 scores supplied in the CVE records: 10.0 Critical for CVE-2026-117551 and CVE-2026-61900; 8.9 High for CVE-2026-117543; 8.2 High for CVE-2026-117544; 7.1 High for CVE-2026-117550; and 5.1 Medium for CVE-2026-117542. They should not be presented as CVSS 3.1 scores or converted into another scoring system.
National Vulnerability Database status should also be interpreted carefully. The associated NVD entries are currently marked Deferred or Awaiting Analysis. For example, the NVD record for CVE-2026-117551 reflects that ongoing status. NVD analysis or presentation may change as its review progresses; the scores cited here remain those in the CVE evidence rather than a claim of completed NVD analysis.
Severity is not the same thing as observed exploitation. As of the reviewed evidence, none of the six CVEs discussed here are listed in CISA's Known Exploited Vulnerabilities catalog, and there is no authoritative confirmation that they have been exploited in the wild. There is also no supported CISA remediation deadline for these issues. That absence should not be used as a reason to postpone patching: a critical RCE and several high-severity flaws justify prompt defensive maintenance on their own.
Patch to 4.1.8 or Later
The immediate outcome for most administrators is straightforward: identify every Joomla site running jDownloads and update any version from 1.0.0 through 4.1.7 to version 4.1.8 or later. Treat frontend upload permissions as a temporary risk-control priority until the update is complete, then validate normal upload, download, and moderation workflows.
Sites that were on jDownloads 4.1.0 through 4.1.5 need additional historical awareness because CVE-2026-61900 was a separate, unauthenticated critical upload RCE fixed in 4.1.6. Reaching 4.1.8 or later addresses both the earlier fixed issue and the five vulnerabilities covered by the 4.1.8 security update. Keep the patch record, review relevant logs, and escalate any signs of unexpected uploads, downloads, file changes, or outbound requests through the site's established incident-response process.
Add comment