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

> An attacker can expose sensitive data by sending an HTTP request with an enterprise ID to the Yealink Meeting Server.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 1 Nov 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-vvmx-2vhq-c359

## What is CVE-2024-48352?

CVE-2024-48352 is a high-severity vulnerability in n/a, published on 1 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Yealink Meeting Server before V26.0.0.67 is vulnerable to sensitive data exposure in the server response via sending HTTP request with enterprise ID.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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

It affects 1 product.


Products: Yealink Yealink Meeting Server.

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

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

## Is CVE-2024-48352 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-24091](https://insights.sbomify.com/CVE-2024-24091/): Command injection in n/a (critical 9.8)
- [CVE-2024-48353](https://insights.sbomify.com/CVE-2024-48353/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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