CVE-2018-25173
Received Received - Intake
SQL Injection in Rmedia SMS 1.0 Allows Data Extraction

Publication date: 2026-03-06

Last updated on: 2026-03-06

Assigner: VulnCheck

Description
Rmedia SMS 1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to extract database information by injecting SQL code through the gid parameter. Attackers can send GET requests to editgrp.php with malicious gid values using EXTRACTVALUE and CONCAT functions to retrieve schema names and sensitive database data.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-06
Last Modified
2026-03-06
Generated
2026-06-16
AI Q&A
2026-03-06
EPSS Evaluated
2026-06-14
NVD
CVE-2018-25173
EUVD
EUVD-2018-21628
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
rmedia sms 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.
Compliance Impact

I don't know

Detection Guidance

[{'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]

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2018-25173. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart