VulnerabilityPublished 24 Feb 2026Updated 26 Feb 2026

CVE-2025-13776: TIK-SOFT Finka-FK · Use of Hard-coded Credentials

Affects TIK-SOFT Finka-FKSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 18.5 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

8.6High

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.5, 16.6, 13.4 +3

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

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
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: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence 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 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
TIK-SOFTFinka-FK	Affected <18.5	Fixed in 18.5
TIK-SOFTFinka-KPR	Affected <16.6	Fixed in 16.6
TIK-SOFTFinka-Płace	Affected <13.4	Fixed in 13.4
TIK-SOFTFinka-Faktura	Affected <18.3	Fixed in 18.3
TIK-SOFTFinka-Magazyn	Affected <8.3	Fixed in 8.3
TIK-SOFTFinka-STW	Affected <12.3	Fixed in 12.3

AI-suggested

To mitigate CVE-2025-13776, organizations should: 1) Immediately upgrade all affected TIK-SOFT Finka software to the fixed versions specified (e.g., Finka-FK 18.5, Finka-KPR 16.6, etc.) to eliminate the use of hard-coded credentials. 2) Restrict local network access to systems running vulnerable Finka products by implementing strict network segmentation, firewall rules, and access control lists to limit exposure to trusted users and devices only. 3) Monitor network traffic for unauthorized Firebird database connections or anomalous activity indicative of credential misuse. 4) Conduct internal audits to identify any unauthorized database access or data modifications that may have occurred prior to patching. 5) Where possible, replace default or hard-coded credentials with unique, securely stored credentials and enforce strong authentication mechanisms. 6) Educate IT and security teams about the risk of hard-coded credentials and the importance of secure credential management in software development and deployment. 7) Implement intrusion detection/prevention systems (IDS/IPS) tuned to detect Firebird protocol anomalies. 8) Regularly review and update network architecture to minimize the attack surface, especially for critical financial and operational systems. These steps go beyond generic patching by emphasizing network-level controls, monitoring, and credential hygiene.

Description

Multiple Finka programs use hard-coded Firebird database credentials (shared across all instances of this software). A malicious attacker in local network who knows default credentials is able to read and edit database content. This vulnerability has been fixed in version: Finka-FK 18.5, Finka-KPR 16.6, Finka-Płace 13.4, Finka-Faktura 18.3, Finka-Magazyn 8.3, Finka-STW 12.3

Impact

The impact of CVE-2025-13776 is substantial for organizations using vulnerable versions of TIK-SOFT Finka products. An attacker with local network access can fully compromise the confidentiality and integrity of the Firebird database, potentially exposing sensitive financial, payroll, inventory, or invoice data depending on the specific Finka product deployed. This can lead to data breaches, unauthorized data manipulation, financial fraud, and disruption of business operations. Since the credentials are hard-coded and shared across all instances, compromise of one installation could facilitate lateral movement within an organization or across organizations using the same software. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing the risk in environments with insufficient network segmentation or monitoring. Although the vulnerability does not directly affect availability, data integrity compromise can indirectly disrupt business processes. Organizations with remote or hybrid work models, or those with less secure internal networks, face higher risks. The absence of known exploits in the wild suggests limited active exploitation currently, but the high CVSS score and ease of exploitation warrant urgent remediation to prevent future attacks.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 19:06 UTC

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats