CVE-2025-12604

7.3

itsourcecode · Online Loan Management System

A SQL injection vulnerability exists in the Online Loan Management System 1.0 via the loan_id parameter in load_fields.php, allowing remote unauthenticated attackers to manipulate database queries.

Executive summary

The itsourcecode Online Loan Management System 1.0 contains a critical SQL injection vulnerability that allows remote, unauthenticated attackers to execute arbitrary database commands.

Vulnerability

This vulnerability is a SQL injection flaw located in the load_fields.php file, where the loan_id argument is not properly sanitized. An unauthenticated attacker can exploit this remotely to manipulate backend database interactions.

Business impact

The ability for an unauthenticated attacker to perform SQL injection poses a significant risk to data confidentiality and integrity. Successful exploitation could lead to unauthorized access to sensitive loan applicant data, potential data exfiltration, or modification of administrative records, which may cause severe reputational damage and regulatory non-compliance. With a CVSS score of 7.3, this high-severity flaw requires immediate attention to prevent unauthorized database access.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict access to the affected file or disable the vulnerable component if it is not business-critical.

Proactive Monitoring: Review web server access logs for anomalous requests containing SQL syntax or unusual parameters directed toward load_fields.php.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns targeting the loan_id parameter.

Exploitation status

Public Exploit Available: Yes — a published proof-of-concept exists, as documented in the linked GitHub repository.

Analyst recommendation

Given the public availability of exploit material and the lack of a vendor-provided patch, this vulnerability presents an immediate risk to any environment running the affected system. Organizations should prioritize isolating the vulnerable application or implementing strict perimeter controls to prevent exploitation until a secure version is released.

More itsourcecode CVEs all →

History

  1. Disclosed CVE record published
  2. Published in the daily brief high section
  3. Published in the daily brief high section
  4. Published in the daily brief high section
  5. Analyst report written

Sources

Originally found and disclosed by P1K1 (VulDB User), per the CVE Program record.