# CVE-2015-4075: Path traversal in n/a

> Remote attackers can write to arbitrary .ini files in the Joomla Helpdesk Pro plugin via a crafted language.save task.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8v2g-f8jh-wfx5

## What is CVE-2015-4075?

CVE-2015-4075 is a high-severity path traversal vulnerability in n/a, published on 20 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Helpdesk Pro plugin before 1.4.0 for Joomla! allows remote attackers to write to arbitrary .ini files via a crafted language.save task.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2015-4075?

It affects 1 product.


Products: Helpdeskpro Helpdesk Pro.

## How do I fix CVE-2015-4075?

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

## Is CVE-2015-4075 being exploited?

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

Public exploit code:

- Joomla! Component Helpdesk Pro < 1.4.0 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4075 and fix it if it is affected.

What it is: CVE-2015-4075 is a high-severity path traversal vulnerability in n/a, published on 20 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-2015-4075 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-2015-4075/ (Markdown: https://insights.sbomify.com/CVE-2015-4075/index.md)
```

## Sources

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

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