CVE-2025-12608VulnerabilityPublished 3 Nov 2025

CVE-2025-12608: itsourcecode Online Loan Management System · SQL Injection

Affects itsourcecode Online Loan Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
itsourcecode Online Loan Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately implement input validation and sanitization on the 'ID' parameter in /manage_user.php to prevent SQL injection. 2. Refactor the vulnerable code to use parameterized queries or prepared statements to separate SQL logic from data. 3. Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for application connections. 4. Monitor logs and database queries for unusual or suspicious activity indicative of injection attempts. 5. If a patch from the vendor becomes available, apply it promptly. 6. Conduct a comprehensive security review of the entire application to identify and remediate similar injection points. 7. Employ Web Application Firewalls (WAFs) with SQL injection detection rules as an additional protective layer. 8. Educate development teams on secure coding practices to prevent recurrence. 9. Prepare incident response plans specific to data breaches involving financial data. 10. Regularly audit and update third-party components and dependencies to reduce attack surface.

Description

A security flaw has been discovered in itsourcecode Online Loan Management System 1.0. The affected element is an unknown function of the file /manage_user.php. Performing manipulation of the argument ID results in sql injection. The attack is possible to be carried out remotely. The exploit has been released to the public and may be exploited.

Impact

For European organizations, especially financial institutions using the itsourcecode Online Loan Management System, this vulnerability poses significant risks. Exploitation could lead to unauthorized disclosure of sensitive customer financial data, manipulation of loan records, and disruption of loan processing services. This can result in regulatory non-compliance (e.g., GDPR violations), financial losses, reputational damage, and operational downtime. Given the remote and unauthenticated nature of the attack, threat actors can exploit this vulnerability at scale, targeting multiple organizations. The medium severity indicates that while the impact is serious, it may not lead to full system compromise but can still cause substantial harm to data confidentiality and integrity. European financial sectors are heavily regulated and rely on data integrity; thus, this vulnerability could undermine trust and lead to legal consequences if exploited.

Summary

CVE-2025-12608 identifies a SQL injection vulnerability in the itsourcecode Online Loan Management System version 1.0, specifically within an unknown function in the /manage_user.php file. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, allowing an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. This flaw enables attackers to manipulate backend database queries, potentially extracting sensitive user data, modifying records, or deleting critical information. The CVSS 4.0 score of 6.9 reflects a medium severity, with attack vector being network-based, low attack complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. Although no active exploitation has been reported, the public release of an exploit increases the likelihood of attacks. The vulnerability is particularly critical in the context of financial applications like loan management systems, where data integrity and confidentiality are paramount. The lack of available patches necessitates immediate mitigation through secure coding practices such as parameterized queries and input validation, as well as restricting database user permissions to minimize damage potential. Continuous monitoring and incident response readiness are also essential to detect and respond to exploitation attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2025, 02:28 UTC

Technical details

References

Community reviews

Related threats