# CVE-2023-52951: Information disclosure in Synology Note Station Client

> Man-in-the-middle attackers can intercept user credentials due to cleartext transmission in the Synology Note Station Client.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 3 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-qcc6-8w82-xq69

## What is CVE-2023-52951?

CVE-2023-52951 is a medium-severity vulnerability in Synology Note Station Client, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A cleartext transmission of sensitive information vulnerability in Synology Note Station Client before 2.2.4-703 allows man-in-the-middle attackers to obtain user credential.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2023-52951?

It affects 1 product.


Products: Synology Note Station Client.

## How do I fix CVE-2023-52951?

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

## Is CVE-2023-52951 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52951 and fix it if it is affected.

What it is: CVE-2023-52951 is a medium-severity vulnerability in Synology Note Station Client, published on 3 Jun 2026. 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-2023-52951 in the wild and no public exploit code.

Affected product: Synology Note Station Client. 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-2023-52951/ (Markdown: https://insights.sbomify.com/CVE-2023-52951/index.md)
```

## Sources

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

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