OpenSTAManager Time-Based Blind SQL Injection Vulnerability in Article Pricing Module

Vulnerability

A critical time-based blind SQL injection vulnerability has been identified in OpenSTAManager versions through 2.9.8. The issue resides in the article pricing completion handler, where the application inadequately sanitizes the 'idarticolo' parameter before incorporating it into SQL queries. This flaw enables authenticated attackers to inject arbitrary SQL commands, exploiting time-based Boolean inference to extract sensitive information, including complete database contents, user credentials, customer data, and financial records.

Impact

Exploitation of this vulnerability allows for time-based blind SQL injection, where an attacker can execute arbitrary SQL commands and extract data from the database. This includes sensitive information such as user credentials, customer details, and financial records. The vulnerability was confirmed and tested on a live instance of OpenSTAManager version 2.9.8.

Reproduction

To reproduce this vulnerability, an authenticated user must send a GET request to the '/ajax_complete.php?op=getprezzi' endpoint, including a crafted 'idarticolo' parameter that exploits the SQL injection flaw. The injection can be verified by using a payload that causes a time delay, such as 'SLEEP()', which demonstrates the successful execution of the injected SQL code. Once the vulnerability is confirmed, data extraction can be performed by sequentially retrieving database information character by character, leveraging the time-based response to indicate the correctness of each extracted character.

Remediation

Users are advised to update to the latest version of OpenSTAManager, as version 2.9.8 is vulnerable and no patched version is currently available.

Added: Feb 6, 2026, 7:20 PM
Updated: Feb 6, 2026, 10:39 PM

Vulnerability Rating

Custom Algorithm
spread
0.0
impact
2.5
exploitability
4.6
remediation
0.0
relevance
2.8
threat
6.4
urgency
2.9
incentive
0.0

Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.