CVE-2025-10288
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in roncoo roncoo-pay up to 9428382af21cd5568319eae7429b7e1d0332ff40. The impacted element is an unknown function of the file /user/info/list. Performing manipulation results in improper authentication. It is possible to initiate the attack remotely. The exploit has been made public and could be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper authentication vulnerability in roncoo roncoo-pay affecting the /user/info/list endpoint. An attacker can remotely access user information without proper authentication, potentially exposing sensitive user data. The exploit has been publicly disclosed and the vendor has not responded to notifications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm roncoo-pay deploymentIdentify if your application uses the roncoo-pay library or framework. Check project dependencies (pom.xml, build.gradle, or similar), or examine the application banner/identifier in HTTP responses.Affected if The application is running roncoo-pay software.
-
Locate the affected endpointVerify the /user/info/list endpoint exists in your deployed application. This is typically found in the web application's routing configuration or API documentation.Affected if The /user/info/list endpoint is present in your application.
-
Test unauthenticated accessSend an HTTP GET request to /user/info/list without providing any authentication credentials (no session cookie, no JWT token, no API key). Use a tool like curl: curl -v http://yourserver/user/info/listAffected if The endpoint returns user data or a successful response (HTTP 200) without requiring authentication.
-
Inspect authentication configurationReview the security configuration files (such as Spring Security config, web.xml, or equivalent) to confirm whether /user/info/list is explicitly excluded from authentication requirements.Affected if The endpoint is explicitly permitted without authentication in security settings, or no rule exists to protect it.
-
Check network exposureDetermine if the application is accessible from untrusted networks. Review firewall rules, load balancer settings, and whether the application is behind a properly configured authentication gateway.Affected if The application port serving the endpoint is exposed to the internet or untrusted internal networks without additional authentication layers.
You are affected if you run roncoo-pay with the /user/info/list endpoint accessible without any authentication credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and authorization checks on the /user/info/list endpoint. Since no vendor patch is available, internal code review and remediation of the authentication logic is required. Consider disabling the endpoint until fix is applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10288 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data