VORANT. Threat Intelligence Research Sign in Create a free account

SQL injection in SMSEagle SMPP server

routine vulnerability

Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.

SQL injection in SMSEagle firmware SMPP server component allows database manipulation; patch to version 6.11.

CERT Polska disclosed a SQL injection vulnerability in SMSEagle firmware affecting the SMPP server component. The flaw arises from improper sanitization of user input in the SMPP server's database interaction scripts. The vulnerability is isolated to the SMPP server, which maintains a separate dedicated database distinct from the main software database, limiting the attack scope to SMPP server operations. SMSEagle has released version 6.11 to address this issue. No active exploitation in the wild has been reported at the time of disclosure.

Mentioned in this report

Vulnerabilities CVE-2025-10095

Source reporting: https://cert.pl/en/posts/2025/09/CVE-2025-10095

What this brief leaves out

This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.

It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.

A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.

Create a free account   What it costs