# CVE-2025-59716: Information disclosure in n/a

> Unauthenticated attackers can enumerate valid pending guest users by observing differential responses from the registration endpoint.

- **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:** 5 Nov 2025
- **Updated:** 5 Nov 2025
- **Also known as:** GHSA-967j-jc6x-3jm4

## What is CVE-2025-59716?

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

### Official description

ownCloud Guests before 0.12.5 allows unauthenticated user enumeration via the /apps/guests/register/{email}/{token} endpoint. Because of insufficient validation of the supplied token in showPasswordForm, the server responds differently when an e-mail address corresponds to a valid pending guest user rather than a non-existent user.

Weakness: CWE-203 (Observable Discrepancy), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-59716?

It affects 1 product.


Products: Owncloud Guests.

## How do I fix CVE-2025-59716?

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

## Is CVE-2025-59716 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59716 exists.

Public exploit code:

- ownCloud Guests - User Enumeration (nuclei): http/cves/2025/CVE-2025-59716.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59716 and fix it if it is affected.

What it is: CVE-2025-59716 is a medium-severity vulnerability in n/a, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59716 exists.

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-2025-59716/ (Markdown: https://insights.sbomify.com/CVE-2025-59716/index.md)
```

## Sources

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

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