External risk intelligence

SLiMS Bulian SQL Injection Vulnerability in Reporting Module

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-107083

SENAYAN Library Management System (SLiMS) is a web-based application designed to be accessed over a network. As an integrated library management system, it is commonly deployed as a web application reachable by users or administrators, making the application's web interface, including reporting modules, a common internet-facing or intranet-facing surface.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the SENAYAN Library Management System (SLiMS) that could allow unauthorized access and modification of data if exploited. This issue, a form of SQL injection, affects the reporting functionality within the system. The primary concern at this stage is to confirm if this specific system is in use and if it is exposed to potential threats.

A flaw allows attackers to potentially misuse the reporting feature.
This system is used for managing library data.
Confirm if our library system is affected and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted requests to the reporting feature of the SENAYAN Library Management System. This could allow them to manipulate database queries, potentially leading to unauthorized access to sensitive information or disruption of the system.

No authentication required.
Sends malicious input to reporting module.
Database compromise and data alteration.

Live Threat

Current exploitation, exposure, and threat context

SQL Injection in the reporting module could allow an unauthenticated attacker to manipulate the database. This could lead to unauthorized access or modification of sensitive library data.

Database integrity and confidentiality.
Unauthenticated network requests.
Unauthorized data access.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts the SENAYAN Library Management System (SLiMS). Teams responsible for web application infrastructure and the SLiMS application itself should lead the initial triage. The first practical step is to identify all SLiMS deployments, determine their accessibility, and confirm business criticality to prioritize remediation efforts.

Application and infrastructure teams own the issue.
Verify SLiMS instances and their reachability.
Plan remediation based on identified risks.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the SENAYAN Library Management System?

SLiMS is an open-source, web-based application designed to manage library collections and resources. It tracks bibliographic data, circulation, and member information, providing a digital interface for staff to organize their archives and for users to search the library catalog online.

What does CVE-2026-107083 mean by SQL injection?

This vulnerability falls under the CWE-89 weakness class, which happens when software fails to properly filter user input before including it in a database query. In this instance, an attacker can input malicious SQL commands into a specific parameter, tricking the application into running unauthorized database operations.

How can an attacker trigger this vulnerability?

The flaw is triggered by sending a specially crafted web request to the 'fileID' parameter within the reporting module's script. Merely visiting the SLiMS interface or browsing the library catalog without sending these specific malicious requests does not trigger the bug.

Is my instance of SLiMS at risk?

According to Halo Surface Signal, SLiMS is designed for network-based access, making its web interface a common target. If your deployment is reachable via the internet, it faces a higher likelihood of unauthorized access attempts compared to a system restricted strictly to a private, isolated intranet.

What should I do if I run SLiMS Bulian?

Begin by auditing your environment to document every active SLiMS instance and verifying which are accessible over the network. Once your footprint is clear, prioritize these systems based on the sensitivity of the library data they hold and prepare to apply patches or restrict module access once guidance becomes available.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.