CVE-2026-111719
Received Received - Intake

Unauthenticated Payment Record Access in Roncoo-pay

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: VulnCheck

Description
Roncoo-pay through commit 9428382 contains a missing authorization vulnerability in F2FPayController.orderQuery that allows unauthenticated attackers to retrieve payment records by supplying a trxNo parameter. Attackers can guess transaction numbers, a '7' prefix plus a snowflake ID, to obtain the full serialized payment record of any merchant.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-111719
EUVD
EUVD-2026-103011

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
roncoo roncoo-pay 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a missing authorization issue in Roncoo-pay where unauthenticated attackers can retrieve payment records by providing a trxNo parameter. Attackers can guess transaction numbers, which follow a pattern of a '7' prefix plus a snowflake ID, to obtain full serialized payment records of any merchant.

Detection Guidance

To detect this vulnerability, monitor network traffic for unauthorized queries to F2FPayController.orderQuery with a trxNo parameter. Look for patterns where attackers guess transaction numbers starting with '7' followed by a snowflake ID. Check server logs for repeated failed attempts to access payment records.

Impact Analysis

This vulnerability allows attackers to access sensitive payment data without authentication. If you are a merchant using Roncoo-pay, attackers could retrieve your payment records, exposing financial details and potentially leading to fraud or data breaches.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized access to sensitive payment data. GDPR requires protection of personal data, while HIPAA mandates safeguards for financial and health-related information. A breach could result in legal penalties and reputational damage.

Mitigation Strategies

Immediately patch the application to enforce authorization checks in F2FPayController.orderQuery. Block unauthenticated access to this endpoint and validate all requests. Review and restrict access to payment records to prevent unauthorized retrieval.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111719. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart