Unauthenticated impersonation via hard-coded verification key
Published Dec 22, 2025 · Updated Dec 22, 2025
Authentication bypass in Ragic Enterprise Cloud Database allows remote attackers to log in as any user by forging verification data. The authentication verifier trusts information generated with a cryptographic key embedded identically in affected deployments. No credentials or user interaction are required; exploitation grants the impersonated account's database access and permissions.
Summary
What happened
Authentication bypass in Ragic Enterprise Cloud Database allows remote attackers to log in as any user by forging verification data. The authentication verifier trusts information generated with a cryptographic key embedded identically in affected deployments. No credentials or user interaction are required; exploitation grants the impersonated account's database access and permissions.
The record
- CVE
- CVE-2025-15016
- Published
- Dec 22, 2025
- Updated
- Dec 22, 2025
- Vendor
- Ragic
- Product
- Enterprise Cloud Database
- Classifications
- CWE-321, CAPEC-37, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 22, 2025CVE publishedPublication date reported by the CVE source.
- Dec 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo