CVE-2023-7331VulnerabilityPublished 31 Dec 2025Updated 2 Jan 2026

CVE-2023-7331: PKrystian Full-Stack-Bank · SQL Injection

Affects PKrystian Full-Stack-BankSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
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

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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

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

What to do

AI-suggested

1. Apply the official patch identified by commit 25c9965a872c704f3a9475488dc5d3196902199a immediately to all instances of PKrystian Full-Stack-Bank. 2. Conduct a thorough code review of the User Handler component and other database interaction points to ensure all inputs are properly sanitized and parameterized queries are used to prevent SQL injection. 3. Implement strict input validation and whitelist acceptable input formats at both client and server sides. 4. Enforce the principle of least privilege for user accounts, ensuring that high privilege access is tightly controlled and monitored. 5. Deploy database activity monitoring tools to detect anomalous queries indicative of injection attempts. 6. Regularly audit logs for suspicious access patterns or failed injection attempts. 7. Educate developers and administrators on secure coding practices related to database interactions. 8. Consider deploying Web Application Firewalls (WAF) with SQL injection detection capabilities as an additional layer of defense. 9. Maintain an up-to-date asset inventory to quickly identify affected systems given the rolling release model. 10. Prepare incident response plans specific to database compromise scenarios to minimize impact if exploitation occurs.

Description

A vulnerability was detected in PKrystian Full-Stack-Bank up to bf73a0179e3ff07c0d7dc35297cea0be0e5b1317. This vulnerability affects unknown code of the component User Handler. Performing manipulation results in sql injection. It is possible to initiate the attack remotely. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The patch is named 25c9965a872c704f3a9475488dc5d3196902199a. It is suggested to install a patch to address this issue.

Impact

For European organizations, particularly financial institutions using PKrystian Full-Stack-Bank, this vulnerability poses a risk of unauthorized data access or manipulation, potentially leading to financial fraud, data breaches, or service disruption. The compromise of banking data could erode customer trust and lead to regulatory penalties under GDPR and other financial regulations. Since the attack requires high privileges, the threat is somewhat mitigated by internal access controls; however, insider threats or compromised credentials could enable exploitation. The rolling release nature of the software means that unpatched instances may exist, increasing exposure. The impact on confidentiality is moderate due to partial data exposure potential, integrity impact is moderate as data could be altered, and availability impact is also moderate if database operations are disrupted. The medium severity suggests that while the threat is not immediately critical, it requires timely remediation to prevent escalation. European banks with high digital transaction volumes and interconnected systems are particularly vulnerable to cascading effects from such an exploit.

Summary

CVE-2023-7331 is an SQL injection vulnerability identified in the User Handler component of the PKrystian Full-Stack-Bank software, affecting versions up to commit bf73a0179e3ff07c0d7dc35297cea0be0e5b1317. This vulnerability arises from improper sanitization or validation of user-supplied input used in SQL queries, allowing an attacker to inject malicious SQL code remotely. The vulnerability can be exploited without user interaction but requires the attacker to have high privileges, indicating that some form of authentication or elevated access is necessary before exploitation. The impact includes potential unauthorized reading, modification, or deletion of sensitive banking data, which could compromise confidentiality, integrity, and availability of the system. The product's rolling release model means traditional versioning is not applicable, but a patch identified by commit 25c9965a872c704f3a9475488dc5d3196902199a addresses the issue. No known exploits have been reported in the wild, but the vulnerability remains a significant risk due to the critical nature of banking data and services. The CVSS 4.0 score of 5.1 reflects medium severity, with network attack vector, low complexity, no user interaction, and limited scope impact. The vulnerability does not affect system components beyond the User Handler, and no supply chain or third-party dependencies are indicated. Organizations using this software should prioritize patching and review their database query handling to prevent injection attacks.

References

Community reviews

Loading reviews…