/

CVE-2026-73327

Severity:

HIGH RISK

(7.6)

Path Traversal (CWE-22) in Joomla Update Extension

CVE-2026-73327

Received

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Persistent Remote Code Execution

Severity:

HIGH RISK

(7.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A path traversal vulnerability in Joomla's com_joomlaupdate extension allows a crafted archive to place files outside the intended extraction directory. When a Super User is induced to process the archive, an attacker may plant executable PHP files and achieve persistent remote code execution.

Affected context

The issue occurs in Joomla 6.1.1 deployments using the com_joomlaupdate extension when archive extraction processes entry names without sufficiently constraining their resulting filesystem paths. Exploitation depends on a privileged user being induced to handle a malicious archive through the affected update workflow.

Exploit preconditions

  • Attack surface: Archive extraction in the com_joomlaupdate update workflow - Required access: Ability to supply or influence an archive and induce a

Super User to process it

  • Trigger point: Extraction of archive entries by the extract.php routine - Why exploitation is possible: Entry names containing traversal elements or

absolute paths may resolve outside the intended destination directory

Why this happens

The underlying bug is insufficient canonicalization and destination-boundary enforcement for archive entry paths. When extracted filenames are trusted without verifying that their normalized paths remain beneath the intended root, attacker-controlled archive metadata can redirect writes elsewhere on the filesystem. This behavior maps to CWE-22, Improper Limitation of a Pathname to a Restricted Directory, also known as path traversal.

Potential impact

  • An attacker may write files outside the intended extraction directory
  • Planted server-side scripts could enable persistent remote code execution
  • Website content, configuration, or application data could be modified
  • Compromised files could support persistence or further application abuse

General mitigation guidance

Mitigation generally centers on treating archive entry names as untrusted and enforcing a secure extraction boundary. Defensive patterns include resolving and validating normalized paths before writing, rejecting absolute and traversal-based names, using extraction libraries with containment protections, and applying allowlists for permitted file types and locations. Update workflows can reduce trust in user-provided archives, use isolated temporary directories, restrict write permissions, and run application processes with only the privileges required for their tasks.

How teams detect issues like this

Detection approaches include static analysis for archive extraction APIs that write paths without canonicalization or containment checks, code review for direct concatenation of archive names with destination directories, and testing with traversal and absolute-path cases in isolated environments. Runtime monitoring can alert on unexpected writes outside designated temporary or update directories, while policy enforcement can require approved archive handling libraries and security tests for privileged update workflows.

Sources

SourceLink
github.comgithub.com/joomla/joomla-cms
github.comgithub.com/joomla/joomla-cms/commit/9678a171d37e1e10ca75c9124bdafe20fe14fa5b
github.comgithub.com/joomla/joomla-cms/pull/48057
vulncheck.comvulncheck.com/advisories/joomla-zip-slip-path-traversal-via-com-joomlaupdate-extract-php

Frequently asked

questions

It is conditionally exploitable. An attacker generally must be able to provide

or influence a malicious archive and persuade a Super User to process it

through the affected update functionality.

The key requirement is access to the archive input or update workflow, together

with a privileged user willing to trigger extraction. Direct filesystem access

is not necessarily required.

Normalize every archive entry path and verify that its final location remains

within a dedicated extraction directory before writing any file. Reject

absolute paths and traversal components by default.

Use archive APIs with built-in path-containment protections, apply least

privilege to update processes, isolate extraction into temporary directories,

and include adversarial archive-path tests in code review and CI pipelines.

Find out what's already
exploitable in your codebase.