Skip to main content

Interuse i-Bos CVE-2026-59508

| EUVDEUVD-2026-97110 MEDIUM
SQL Injection (CWE-89)
2026-10-11 INCD GHSA-8x2r-fqxm-ph3g
5.9
CVSS 3.1 · Vendor: INCD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach i-Bos web endpoint
  2. Delivery
    Submit crafted SQL payload
  3. Exploit
    Exploit injectable parameter
  4. Execution
    Iteratively extract query output
  5. Impact
    Exfiltrate sensitive database records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires network access to the i-Bos 3.0 application and an injectable input parameter reachable without authentication (PR:N). The HIGH attack complexity (AC:H) is the key limiting factor: successful exploitation depends on a condition not fully under the attacker's control - consistent with blind/inferential SQL injection needing many requests, specific database back-end behavior, or a particular application state rather than a direct, reliable single-request injection. Impact is limited to confidentiality (data disclosure); per the provided vector there is no integrity or availability impact, so this does not by itself yield data tampering or service disruption. Exploitation is constrained to the i-Bos 3.0 version specifically.

Impact

This is a moderate-severity SQL injection (CWE-89) in Interuse i-Bos 3.0 with a CVSS 3.1 base score of 5.9. The vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N indicates a network-reachable, unauthenticated (PR:N) flaw, but the HIGH attack complexity (AC:H) and confidentiality-only impact (C:H/I:N/A:N) significantly temper the real-world risk - the AC:H suggests the attacker must satisfy a condition outside their control (e.g. a blind/time-based injection or specific input state) rather than a trivial single-shot injection, which is why the score lands at 5.9 rather than the ~9+ a clean unauthenticated SQLi would score. No EPSS probability, CISA KEV listing, or public exploit code is present in the provided data, so there is no evidence of active exploitation or weaponization; this is a disclosure-stage finding from Israel's INCD. Note one internal tension worth verifying with the vendor: a SQL injection rated I:N/A:N (no integrity or availability impact) is unusual, as injection flaws frequently permit data modification - the classification implies read-only data exfiltration, but confirm whether write/stacked-query vectors were simply not assessed. Overall this is a 'high-CVSS-is-actually-moderate' case: a genuine vulnerability, but not an urgent, mass-exploitable priority absent exploitation signals.

Exploit ScenarioDerived

A remote, unauthenticated attacker submits crafted input to an injectable parameter in the i-Bos 3.0 web interface to manipulate backend SQL queries and read sensitive database contents. Because CVSS complexity is HIGH, the attacker likely relies on a blind or time-based technique requiring multiple iterative requests rather than a single payload. No public exploit code or active exploitation has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 11, 2026

SQL injection (CWE-89) in Interuse i-Bos 3.0 lets unauthenticated remote attackers pass crafted input that is concatenated into SQL statements, potentially exposing database contents. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N, base 5.9) shows confidentiality as the primary impact, with attack complexity rated High because reliable exploitation depends on a condition not fully under the attacker's control - characteristic of blind/inferential SQL injection, back-end-specific behavior, or a particular application state rather than a single deterministic request. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the report originates from Israel's INCD advisory stream.

RemediationAI

No vendor-released patch was identified at time of analysis, so remediation must start with the vendor: contact Interuse for a fixed i-Bos 3.0 build and monitor the INCD advisory listing (https://www.gov.il/en/departments/dynamiccollectors/cve_advisories_listing?skip=0) for updated guidance. Until a fix exists, apply compensating controls: deploy a WAF with tuned SQL-injection signatures in front of i-Bos (trade-off: false positives on legitimate input and potential bypass via encoding, so it must be paired with logging and rule tuning); restrict network reachability of the i-Bos application to trusted networks or VPN clients only (trade-off: reduces legitimate remote access and requires network re-architecture); and run the application's database connection under a least-privilege account limited to the specific tables and operations it needs, which caps what an injection can read (trade-off: may break features relying on broader permissions and requires schema review). Additionally, since the vector shows PR:N, treat any internet-facing or broadly reachable i-Bos instance as the priority: enforce authentication and input validation at the reverse proxy, enable verbose database query logging with alerting on anomalous SQL patterns to detect blind-injection retry bursts, and rotate database credentials after any suspected exposure. Because the assessed impact includes confidentiality (C:H) and limited integrity effects (I:L), verify database contents for tampering if injection is suspected.

Affected VersionsENISA

i-Bos 3.0

Affected Packages

euvd i_bos no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-89, Improper Neutralization of Special Elements used in an SQL Command: user-supplied input is not safely separated from SQL syntax (for example, string concatenation instead of parameterized statements or stored procedures), so injected metacharacters can alter query logic. The CPE cpe:2.3:a:interuse:i-bos:*:*:*:*:*:*:*:* identifies the Interuse i-Bos product line, and the advisory explicitly scopes the flaw to version 3.0, meaning other releases are not confirmed affected by the available data. The network vector (AV:N) with PR:N indicates the injectable parameter is reachable over the network without prior authentication, while AC:H reflects an exploitation path that is not fully attacker-controlled - typically a blind/boolean- or time-based injection requiring many iterative requests, or one that only succeeds against specific database back-ends or application states. The scope is unchanged (S:U), so a successful injection is confined to the application's own security authority and its database access, with the assessed impact capped at data disclosure (C:H) plus limited integrity effects (I:L) and no availability impact (A:N).

Know when I Bos gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (INCD) PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable unauthenticated SQLi (AV:N/PR:N); AC:H retained for a blind/condition-dependent injection; C:H for DB read, with I:L added since injection commonly permits some data modification.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (INCD).

CVSS VectorVendor: INCD

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Interuse i-Bos.

This issue affects i-Bos: 3.0.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Low
niche Israeli vendor product, no broad enterprise or global footprint
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy