Skip to content
Critical SQL Injection Vulnerability in Arraytics Booktics (CVE-2026-109894)

Critical SQL Injection Vulnerability in Arraytics Booktics (CVE-2026-109894)

First seen 19 Oct 2026, 05:17 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 19, 2026 at 05:49 UTC
  • •CVE-2026-109894 is a critical SQL Injection vulnerability in Arraytics Booktics.
  • •The flaw affects versions up to 1.0.29 and has a CVSS score of 9.3.
  • •No public proof-of-concept or exploitation has been confirmed as of now.

A critical SQL Injection vulnerability (CVE-2026-109894) has been identified in Arraytics Booktics, affecting versions up to 1.0.29. This flaw allows unauthenticated attackers to execute arbitrary SQL queries remotely, potentially leading to data exfiltration and denial of service. The vulnerability has a CVSS score of 9.3, indicating high confidentiality impact and low availability impact. No public proof-of-concept or evidence of exploitation has been reported as of now. Users are advised to upgrade to a version beyond 1.0.29 and implement input validation to mitigate risks. The vulnerability was published on 2026-10-18, and no official patch has been released yet. Security advisories recommend deploying web application firewalls and restricting database permissions as interim measures.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-18
CVE-2026-109894 published
Arraytics Booktics vulnerability disclosed, allowing SQL Injection attacks on versions up to 1.0.29.
Feedly

More articles in this cluster (2)

Following this threat?

Track Arraytics and CVE-2026-109894 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (6)

1 / 4

Common questions

Which versions of Arraytics Booktics are affected?
The vulnerability affects all versions up to and including 1.0.29.
Is there a patch available for this vulnerability?
No official patch or remediation guidance has been released yet.
What immediate actions should be taken?
Upgrade to a version beyond 1.0.29 and implement input validation to mitigate the risk.