# CVE-2023-47102: Information disclosure in n/a

> UrBackup Server allows attackers to enumerate valid user accounts by distinguishing between invalid and valid usernames via error messages.

- **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:** 7 Nov 2023
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-q8x9-r7fc-qfjv

## What is CVE-2023-47102?

CVE-2023-47102 is a medium-severity vulnerability in n/a, published on 7 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UrBackup Server 2.5.31 allows brute-force enumeration of user accounts because a failure message confirms that a username is not valid.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Urbackup Urbackup Server.

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

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

## Is CVE-2023-47102 being exploited?

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

Public exploit code:

- https://github.com/quantiano/cve-2023-47102 (github_poc): https://github.com/quantiano/cve-2023-47102

## Other vulnerabilities in n/a

- [CVE-2017-16950](https://insights.sbomify.com/CVE-2017-16950/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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