CVE-2018-25173
SQL Injection in Rmedia SMS 1.0 Allows Data Extraction
Publication date: 2026-03-06
Last updated on: 2026-03-06
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rmedia | sms | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an SQL injection in Rmedia SMS version 1.0, specifically in the editgrp.php script through the gid GET parameter.
An unauthenticated attacker can inject malicious SQL code via the gid parameter, allowing them to execute arbitrary SQL commands on the database.
This injection can be used to extract sensitive database information such as schema names and other data by leveraging SQL functions like EXTRACTVALUE and CONCAT.
How can this vulnerability impact me? :
The vulnerability allows attackers to extract sensitive information from the database without authentication.
- Unauthorized access to database schema and data.
- Potential exposure of confidential or personal information stored in the database.
- Compromise of data integrity due to partial control over database queries.
- Increased risk of further attacks leveraging the extracted data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This SQL injection vulnerability can be detected by sending crafted GET requests to the vulnerable script editgrp.php with malicious gid parameter values that attempt to extract database information.'}, {'type': 'paragraph', 'content': 'A typical detection command involves using curl or a similar HTTP client to send a request with an SQL injection payload in the gid parameter, for example:'}, {'type': 'list_item', 'content': 'curl "http://target/editgrp.php?gid=1\' AND EXTRACTVALUE(1, CONCAT(0x7e, (SELECT schema_name FROM INFORMATION_SCHEMA.SCHEMATA LIMIT 0,1), 0x7e))-- -"'}, {'type': 'paragraph', 'content': 'If the response contains database schema names or error messages related to SQL functions like EXTRACTVALUE, it indicates the presence of the vulnerability.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
I don't know