# CVE-2015-4071: Information disclosure in n/a

> Remote attackers can read arbitrary support tickets by guessing ticket IDs, exposing sensitive user data in Joomla Helpdesk Pro Plugin.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 18 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mwmc-6chq-x9m4

## What is CVE-2015-4071?

CVE-2015-4071 is a medium-severity vulnerability in n/a, published on 18 Aug 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 read the support tickets of arbitrary users via obtaining the target ticketId, and navigating to http://{target}/component/helpdeskpro/?view=ticket&id={ticketId}.

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

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

It affects 1 product.


Products: Helpdesk Pro Project Helpdesk Pro.

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

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

## Is CVE-2015-4071 being exploited?

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

Public exploit code:

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

## Other vulnerabilities in n/a

- [CVE-2015-4073](https://insights.sbomify.com/CVE-2015-4073/): SQL injection in n/a (critical 9.8)
- [CVE-2015-4074](https://insights.sbomify.com/CVE-2015-4074/): Path traversal in n/a (high 7.5)
- [CVE-2015-4072](https://insights.sbomify.com/CVE-2015-4072/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-4071 is a medium-severity vulnerability in n/a, published on 18 Aug 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-4071 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-4071/ (Markdown: https://insights.sbomify.com/CVE-2015-4071/index.md)
```

## Sources

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

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