# CVE-2019-25762: Joomla! Component JoomProject 1.1.3.2 Information Disclosure

> Unauthenticated attackers can retrieve sensitive user data including IDs, names, and emails via a vulnerable JSON endpoint in the JoomProject component.

- **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:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-c57g-h86v-mmh8

## What is CVE-2019-25762?

CVE-2019-25762 is a high-severity vulnerability in Joomboost JoomProject, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla! Component JoomProject 1.1.3.2 contains an information disclosure vulnerability that allows unauthenticated attackers to access sensitive user data by exploiting the projects endpoint. Attackers can send requests to index.php with option=com_jpprojects&view=projects&tmpl=component&format=json parameters to retrieve user IDs, names, and email addresses in JSON format.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-25762?

It affects 1 product.


Products: Joomboost Joomproject.

## How do I fix CVE-2019-25762?

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

## Is CVE-2019-25762 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25762 and fix it if it is affected.

What it is: CVE-2019-25762 is a high-severity vulnerability in Joomboost JoomProject, published on 19 Jun 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-2019-25762 exists.

Affected product: Joomboost JoomProject. 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-2019-25762/ (Markdown: https://insights.sbomify.com/CVE-2019-25762/index.md)
```

## Sources

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

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