CVE-2018-25173

8.2

Rmedia · SMS

Rmedia SMS 1.0 suffers from an SQL injection vulnerability in the editgrp.php script, allowing unauthenticated attackers to extract sensitive database information via the gid parameter.

Executive summary

A critical SQL injection vulnerability in Rmedia SMS 1.0 allows unauthenticated remote attackers to extract sensitive database information.

Vulnerability

This is an SQL injection vulnerability (CWE-89) located in the editgrp.php script. Unauthenticated attackers can inject malicious SQL code through the gid parameter using GET requests to extract database schema names and sensitive data.

Business impact

The ability for an unauthenticated attacker to perform arbitrary SQL queries against the backend database poses a severe risk to data confidentiality. An attacker could potentially exfiltrate user credentials, administrative configurations, or other proprietary information stored within the database. Given the CVSS score of 8.2, this vulnerability represents a high-severity risk that could lead to full database compromise and significant reputational damage.

Remediation

Immediate Action: There is no official patch available for Rmedia SMS 1.0. Organizations currently using this software should immediately restrict access to the application or discontinue its use.

Proactive Monitoring: Review web server access logs for suspicious GET requests targeting editgrp.php, specifically those containing SQL syntax characters like single quotes, parentheses, or keywords such as SELECT, CONCAT, and EXTRACTVALUE.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection patterns, specifically targeting common exploitation strings in the gid parameter.

Exploitation status

Public Exploit Available: Yes, a functional proof-of-concept exists via the Exploit Database (EDB-ID 45855).

Analyst recommendation

Due to the lack of an official vendor patch and the availability of public exploit code, Rmedia SMS 1.0 must be considered insecure for production environments. Security teams should prioritize identifying any instances of this software and decommissioning it or migrating to a supported, secure alternative immediately to prevent potential data exfiltration.

Sources

Originally found and disclosed by Ihsan Sencan, per the CVE Program record.