Security Resilience

CVE-2025-0967

SQLi in Fabian Chat System 1.0

Public PoCSQLi
Published
02 February 2025
Modified
23 October 2025
Patch / advisory
CVSS Score v4 5.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0060 48th percentile
Risk Priority 34 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-0967 is a medium-severity Injection (CWE-74) vulnerability in Fabian Chat System. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-0967 is a critical SQL injection vulnerability in code-projects Chat System 1.0, affecting the processing of the file /user/add_chatroom.php. The issue arises from improper handling of the chatname and chatpass arguments, allowing manipulation that leads to SQL injection as classified under CWE-74 and CWE-89. It carries a CVSS v3.1 base score of 6.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L) and was published on 2025-02-02.

The vulnerability can be exploited remotely by an attacker with low privileges, such as a registered user, requiring low attack complexity and no user interaction. Successful exploitation enables limited confidentiality, integrity, and availability impacts through SQL injection, potentially allowing unauthorized data access, modification, or disruption within the chat system's database.

Advisories and references, including those from VulDB (ctiid.294359, id.294359) and a GitHub proof-of-concept at Team-intN18-SoybeanSeclab/CVE/sqlinject1.md, confirm the exploit has been publicly disclosed and may be used. The vendor site at code-projects.org provides additional context, though no specific patches or mitigations are detailed in the available information. Security practitioners should review these sources for updates and apply input validation or database query parameterization as general SQL injection defenses.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability was found in code-projects Chat System 1.0 and classified as critical. This issue affects some unknown processing of the file /user/add_chatroom.php. The manipulation of the argument chatname/chatpass leads to sql injection. The attack may be initiated remotely. The…

more

exploit has been disclosed to the public and may be used.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-9009Same vendor: Fabian
CVE-2023-7126Same vendor: Fabian
CVE-2023-7139Same vendor: Fabian
CVE-2023-7111Same vendor: Fabian
CVE-2024-7682Same vendor: Fabian
CVE-2023-7106Same vendor: Fabian
CVE-2023-7140Same vendor: Fabian
CVE-2024-7808Same vendor: Fabian
CVE-2023-7137Same vendor: Fabian
CVE-2024-8218Same vendor: Fabian

Affected Assets

fabian
chat system
1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover SQLi flaws before deployment but does not stop their introduction.

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

Secure engineering principles require parameterized queries and input sanitization that structurally eliminate SQLi.

System monitoring can identify attempted SQLi exploitation via anomalous queries after the weakness exists.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.

PR.AT-02 partial match
blocks

Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.

finds

Monitoring activities can identify active injection attacks after they occur.

prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

finds

created from the owner's anchor; an owner grade is a row and does not wait for an instrument (Mythos 2026-09-29T15:58Z).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.

References