# CVE-2017-2550: Information disclosure in Easy Joomla Backup

> An attacker can download sensitive site backups by guessing predictable filenames stored in the web root.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j87p-7jp3-jch5

## What is CVE-2017-2550?

CVE-2017-2550 is a high-severity vulnerability in kubik-rubik Easy Joomla Backup, published on 8 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in Easy Joomla Backup v3.2.4. The software creates a copy of the backup in the web root with an easily guessable filename.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-2550?

It affects 1 product.


Products: Kubik-Rubik Easy Joomla Backup.

## How do I fix CVE-2017-2550?

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

## Is CVE-2017-2550 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2550 and fix it if it is affected.

What it is: CVE-2017-2550 is a high-severity vulnerability in kubik-rubik Easy Joomla Backup, published on 8 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2550 in the wild and no public exploit code.

Affected product: kubik-rubik Easy Joomla Backup. 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-2017-2550/ (Markdown: https://insights.sbomify.com/CVE-2017-2550/index.md)
```

## Sources

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

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