# CVE-2024-24720: Information disclosure in n/a

> An attacker can determine if specific users exist on the system via the forgot password function, facilitating targeted attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/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:** 27 Feb 2024
- **Updated:** 30 May 2025
- **Also known as:** GHSA-8cpv-pp42-ppmr

## What is CVE-2024-24720?

CVE-2024-24720 is a medium-severity vulnerability in n/a, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Forgot password function in Innovaphone PBX before 14r1 devices. It provides information about whether a user exists on a system.

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

## Which versions are affected by CVE-2024-24720?

It affects 1 product.


Products: Innovaphone Innovaphone Pbx.

## How do I fix CVE-2024-24720?

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

## Is CVE-2024-24720 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5335](https://insights.sbomify.com/CVE-2014-5335/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2024-24721](https://insights.sbomify.com/CVE-2024-24721/): Auth bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24720 and fix it if it is affected.

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

## Sources

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

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