CVE-2025-12617VulnerabilityPublished 3 Nov 2025Updated 24 Feb 2026

CVE-2025-12617: itsourcecode Billing System · SQL Injection

Affects itsourcecode Billing SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 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 40% 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-25.

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 Billing System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately restrict external access to the /admin/app/login_crud.php endpoint via network controls such as firewalls or VPNs to limit exposure. 2. Implement Web Application Firewall (WAF) rules to detect and block SQL injection payloads targeting the Password parameter. 3. Conduct thorough input validation and parameterized queries or prepared statements in the affected code to prevent SQL injection. 4. Monitor logs for suspicious activity related to login attempts and SQL injection patterns. 5. Engage with the vendor or community to obtain or develop patches and apply them as soon as available. 6. If patching is not immediately possible, consider isolating the billing system within a segmented network zone with strict access controls. 7. Educate system administrators and security teams about this vulnerability and the importance of rapid response. 8. Regularly back up billing data and verify backup integrity to enable recovery in case of data tampering.

Description

A flaw has been found in itsourcecode Billing System 1.0. This affects an unknown function of the file /admin/app/login_crud.php. Executing a manipulation of the argument Password can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used.

Impact

The SQL injection vulnerability in the itsourcecode Billing System can lead to unauthorized access to sensitive billing and customer data, potentially resulting in data breaches and financial fraud. Attackers could manipulate database queries to extract confidential information, alter billing records, or disrupt service availability. This could damage organizational reputation, lead to regulatory penalties, and cause operational disruptions. Since the vulnerability can be exploited remotely without authentication, any exposed instance of the affected software is at risk. The scope is limited to organizations using version 1.0 of this specific billing system, but the impact on those organizations can be substantial, especially if billing data integrity or confidentiality is compromised. The absence of patches increases the urgency for mitigation to prevent exploitation attempts, particularly as exploit code is publicly available.

Summary

CVE-2025-12617 is a SQL injection vulnerability identified in itsourcecode Billing System version 1.0, specifically within the /admin/app/login_crud.php file. The vulnerability arises from improper sanitization or validation of the Password parameter, allowing an attacker to inject malicious SQL queries remotely without requiring authentication or user interaction. This flaw enables attackers to manipulate backend database queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has a CVSS 4.0 base score of 6.9, indicating medium severity, with an attack vector of network (remote), low attack complexity, no privileges required, and no user interaction needed. The impact on confidentiality, integrity, and availability is low to medium but still significant given the sensitive nature of billing data. No official patches or fixes have been released yet, and although no active exploitation has been observed, the public availability of exploit code increases the risk of attacks. Organizations relying on this billing system should assess their exposure and implement mitigations promptly to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:15 UTC

Technical details

References

Community reviews

Related threats