CVE-2023-54163VulnerabilityPublished 30 Dec 2025Updated 2 Jan 2026

CVE-2023-54163: NLB mKlik Makedonija · SQL Injection

Affects NLB mKlik MakedonijaSource CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

8.8High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% 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:H/VI:L/VA:N/SC:N/SI:N/SA:N

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

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: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
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: None: There is no impact to availability within 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Dec 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.

North Macedonia

What to do

Affected software

Product	Affected	Fixed in
NLB Banka AD Skopje NLB mKlik Makedonija	Affected =3.3.12	Fixed in–

AI-suggested

1. Immediate implementation of input validation and sanitization on all international transfer parameters to prevent injection of malicious SQL code. 2. Refactor the application code to use parameterized queries or prepared statements exclusively, eliminating direct concatenation of user input into SQL commands. 3. Deploy Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the affected endpoints. 4. Conduct thorough code reviews and security testing (including automated and manual penetration testing) focused on input handling in the mobile banking application. 5. Monitor database logs and application logs for unusual query patterns or access anomalies that may indicate exploitation attempts. 6. Engage with NLB Banka AD Skopje to obtain patches or updates addressing this vulnerability as soon as they become available. 7. Educate development and security teams on secure coding practices to prevent similar vulnerabilities in future releases. 8. For organizations integrating or relying on NLB mKlik services, consider additional network segmentation and access controls to limit exposure until the vulnerability is remediated.

Description

NLB mKlik Macedonia 3.3.12 contains a SQL injection vulnerability in international transfer parameters that allows attackers to manipulate database queries. Attackers can inject arbitrary SQL code through unsanitized input to potentially disclose sensitive information from the mobile banking application.

Impact

For European organizations, especially financial institutions and customers connected to NLB Banka AD Skopje or using the NLB mKlik Makedonija application, this vulnerability poses a significant risk of data breach and financial fraud. The unauthorized disclosure of sensitive banking data could lead to identity theft, financial loss, and regulatory penalties under GDPR due to compromised personal data. The integrity of transaction data could be undermined, potentially facilitating fraudulent transfers or manipulation of account information. The reputational damage to the bank and associated financial entities could be severe, impacting customer trust and market position. Given the cross-border nature of banking and financial services in Europe, the vulnerability could also affect partner institutions and customers in other EU countries. The lack of authentication requirement and ease of exploitation increase the likelihood of attacks, which could disrupt banking operations and lead to costly incident response and remediation efforts.

References

Community reviews

Loading reviews…