# CVE-2019-12743: Information disclosure in n/a

> Remote attackers can enumerate valid user accounts by brute-forcing usernames due to response discrepancies in the social network kit.

- **Severity:** Medium 5.3 (`CVSS:3.0/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:** 29 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r8ch-45q6-53xj

## What is CVE-2019-12743?

CVE-2019-12743 is a medium-severity vulnerability in n/a, published on 29 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HumHub Social Network Kit Enterprise v1.3.13 allows remote attackers to find the user accounts existing on any Social Network Kits (including self-hosted ones) by brute-forcing the username after the /u/ initial URI substring, aka Response Discrepancy Information Exposure.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Humhub Social Network Kit.

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

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

## Is CVE-2019-12743 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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