# CVE-2020-13424: The XCloner component before 3.5.4 for Joomla!


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6fqc-xc5h-q49p

## What is CVE-2020-13424?

CVE-2020-13424 is a medium-severity vulnerability in n/a, published on 23 May 2020. 

### Official description

The XCloner component before 3.5.4 for Joomla! allows Authenticated Local File Disclosure.

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

It affects 1 product.


Products: Xcloner Xcloner.

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

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

## Is CVE-2020-13424 being exploited?

There is no known exploitation of CVE-2020-13424 in the wild and no public exploit code.

Public exploit code:

-  Joomla! Plugin XCloner Backup 3.5.3 - Local File Inclusion (Authenticated) (github_poc): https://github.com/mkelepce/CVE-2020-13424

## Other vulnerabilities in n/a

- [CVE-2020-35948](https://insights.sbomify.com/CVE-2020-35948/): Missing authorization in n/a (critical 9.9)
- [CVE-2020-35950](https://insights.sbomify.com/CVE-2020-35950/): Cross-site request forgery in n/a (critical 9.8)
- [CVE-2014-2579](https://insights.sbomify.com/CVE-2014-2579/): Cross-site request forgery in n/a (high 7.6)
- [CVE-2014-2996](https://insights.sbomify.com/CVE-2014-2996/): Command injection in n/a (high 7.1)
- [CVE-2014-2340](https://insights.sbomify.com/CVE-2014-2340/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13424 is a medium-severity vulnerability in n/a, published on 23 May 2020. 
Exploitation: There is no known exploitation of CVE-2020-13424 in the wild and no public exploit code.

Affected product: n/a. 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-13424/ (Markdown: https://insights.sbomify.com/CVE-2020-13424/index.md)
```

## Sources

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

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