# CVE-2020-37219: Joomla com_fabrik 3.9.11 Directory Traversal via image.php

> Unauthenticated attackers can list arbitrary files outside the web root via directory traversal in the Fabrik plugin for Joomla.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-px6w-5x4g-ww8h

## What is CVE-2020-37219?

CVE-2020-37219 is a high-severity path traversal vulnerability in Fabrikar com_fabrik, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla com_fabrik 3.9.11 contains a directory traversal vulnerability that allows unauthenticated attackers to list arbitrary files by manipulating the folder parameter. Attackers can send GET requests to the onAjax_files method with path traversal sequences to enumerate files in system directories outside the intended web root.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2020-37219?


## How do I fix CVE-2020-37219?

No fix has been published for CVE-2020-37219 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-37219 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37219 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37219 and fix it if it is affected.

What it is: CVE-2020-37219 is a high-severity path traversal vulnerability in Fabrikar com_fabrik, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37219 exists.

Affected product: Fabrikar com_fabrik. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-37219/ (Markdown: https://insights.sbomify.com/CVE-2020-37219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-37219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-37219
- OSV: https://osv.dev/vulnerability/CVE-2020-37219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-37219/
Summaries are generated and may contain mistakes; the official description above is the record.