Authenticated database access via recipt_no SQL injection
Published Jul 20, 2025 · Updated Jul 21, 2025
SQL injection in itsourcecode.com Insurance Management System 1.0 allows remote authenticated users to access its database via recipt_no. insertPayment.php uses the POST-supplied recipt_no value in a MySQL query without sanitization or validation, allowing injected SQL clauses to execute. A valid session cookie is required; the published proof of concept demonstrates error-based data extraction and a time-based database delay.
Summary
What happened
SQL injection in itsourcecode.com Insurance Management System 1.0 allows remote authenticated users to access its database via recipt_no. insertPayment.php uses the POST-supplied recipt_no value in a MySQL query without sanitization or validation, allowing injected SQL clauses to execute. A valid session cookie is required; the published proof of concept demonstrates error-based data extraction and a time-based database delay.
The record
- CVE
- CVE-2025-7905
- Published
- Jul 20, 2025
- Updated
- Jul 21, 2025
- Vendor
- itsourcecode.com
- Product
- Insurance Management System
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2025CVE publishedPublication date reported by the CVE source.
- Jul 21, 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=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Authenticated recipt_no SQL injection proof of conceptfunctional · demonstrated
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