VulnerabilityPublished 19 Jan 2024Updated 30 May 2025

CVE-2024-0734: Smsot · SQL Injection

Affects SmsotSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubsmsot`pkg:github/smsot`Other threats	Affected =2.0 =2.1 =2.2 =2.3 =2.4 =2.5 =2.6 =2.7 =2.8 =2.9 =2.10 =2.11 =2.12	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, European organizations should implement immediate compensating controls. First, restrict access to the /get.php endpoint by applying network-level controls such as IP whitelisting or VPN requirements to limit exposure to trusted users only. Second, deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'tid' parameter. Third, conduct thorough input validation and parameterization within the application code if source code access is available, ensuring that all user inputs are sanitized and use prepared statements. Fourth, monitor logs for unusual query patterns or repeated failed attempts to exploit the 'tid' parameter. Fifth, perform regular vulnerability scanning and penetration testing focused on SQL injection vectors. Finally, maintain an incident response plan to quickly address any detected exploitation attempts. Organizations should also engage with Smsot vendors or communities to track patch releases and apply updates promptly once available.

Description

A vulnerability was found in Smsot up to 2.12. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /get.php. The manipulation of the argument tid leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-251557 was assigned to this vulnerability.

Impact

For European organizations, the impact of this vulnerability can be significant depending on the deployment of Smsot in their environments. Successful exploitation can lead to unauthorized data disclosure, data tampering, and potential service disruption. This is particularly critical for organizations handling sensitive personal data under GDPR regulations, as data breaches could result in regulatory penalties and reputational damage. The remote exploitability without user interaction increases the risk of automated attacks or mass scanning campaigns targeting vulnerable Smsot instances. Industries such as telecommunications, customer service platforms, or any sector using Smsot for messaging or related services could be affected. The medium severity rating suggests that while the vulnerability is serious, exploitation may require some privileges or specific conditions, potentially limiting widespread impact. However, the public disclosure of exploit details raises the urgency for European organizations to assess their exposure and implement mitigations promptly to avoid data breaches or operational disruptions.

Summary

CVE-2024-0734 is a SQL Injection vulnerability identified in Smsot versions up to 2.12. The vulnerability resides in the /get.php file, specifically in the handling of the 'tid' parameter. An attacker can manipulate this parameter to inject malicious SQL code, which the backend database executes. This flaw allows remote exploitation without requiring user interaction, but it does require some level of privileges (PR:L) as indicated by the CVSS vector. The vulnerability affects the confidentiality, integrity, and availability of the affected system, as attackers can potentially extract sensitive data, modify or delete records, or disrupt service availability. The CVSS score of 6.3 categorizes this as a medium severity issue. Although no public exploits are currently known to be actively used in the wild, the exploit details have been disclosed, increasing the risk of future exploitation. The vulnerability is classified under CWE-89, which is a common and well-understood injection flaw that arises from improper sanitization or parameterization of SQL queries. Smsot is the affected product, but no vendor or project information is provided, which may complicate patch management. The lack of available patches or mitigation links suggests that organizations must rely on other defensive measures until an official fix is released.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 16:43 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats