# CVE-2025-10287: roncoo roncoo-pay orderQuery direct request

> Attackers can bypass authorization to query order details directly via the orderQuery endpoint, exposing sensitive transaction data.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2025
- **Updated:** 12 Sep 2025
- **Also known as:** GHSA-rm4g-r867-8r8c

## What is CVE-2025-10287?

CVE-2025-10287 is a low-severity missing authorization vulnerability in roncoo-pay, published on 12 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in roncoo roncoo-pay up to 9428382af21cd5568319eae7429b7e1d0332ff40. The affected element is an unknown function of the file /auth/orderQuery. Such manipulation of the argument orderNo leads to direct request. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit has been disclosed to the public and may be used. 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-425 (Direct Request)

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


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

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

## Is CVE-2025-10287 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10287 is a low-severity missing authorization vulnerability in roncoo-pay, published on 12 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10287 exists.

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

## Sources

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

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