# CVE-2025-10992: roncoo roncoo-pay lookupList improper authorization

> Remote attackers can access user information via the lookupList endpoint due to improper authorization checks in the roncoo-pay application.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-857m-r47g-pcm9

## What is CVE-2025-10992?

CVE-2025-10992 is a medium-severity missing authorization vulnerability in roncoo-pay, published on 26 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in roncoo roncoo-pay up to 9428382af21cd5568319eae7429b7e1d0332ff40. Affected is an unknown function of the file /user/info/lookupList. Executing manipulation can lead to improper authorization. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-10992 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10992 is a medium-severity missing authorization vulnerability in roncoo-pay, published on 26 Sep 2025. 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-2025-10992 in the wild and no public exploit code.

Affected product: roncoo-pay. 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-10992/ (Markdown: https://insights.sbomify.com/CVE-2025-10992/index.md)
```

## Sources

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

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