CVE-2018-25199
SQL Injection in OOP CMS BLOG 1.0 Enables Data Extraction
Publication date: 2026-03-06
Last updated on: 2026-03-11
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tomalofficial | php_oop_cms_blog | 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?
[{'type': 'paragraph', 'content': 'CVE-2018-25199 is a set of multiple SQL injection vulnerabilities found in OOP CMS BLOG version 1.0. These vulnerabilities allow unauthenticated attackers to inject malicious SQL code through various parameters in the application, specifically the "search" parameter in search.php, the "pageid" parameter in page.php, and the "id" parameter in posts.php.'}, {'type': 'paragraph', 'content': 'By exploiting these injection points, attackers can execute arbitrary SQL queries on the backend database. This enables them to extract sensitive information such as table names, schema names, database credentials, and other metadata from the database.'}, {'type': 'paragraph', 'content': 'The vulnerability is classified under CWE-89, which refers to improper neutralization of special elements used in an SQL command, commonly known as SQL injection.'}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized disclosure of sensitive database information. Attackers can extract critical data such as database table names, schema names, user credentials, and other confidential information.
Such unauthorized access can lead to further attacks, data breaches, and compromise of the entire application and its data integrity.
Because the vulnerability allows execution of arbitrary SQL commands without authentication, it poses a high security risk with a CVSS v4 base score of 8.8, indicating a critical severity level.
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 vulnerability can be detected by testing the vulnerable parameters for SQL injection using crafted SQL payloads. Specifically, the parameters to test are "search" in search.php, "pageid" in page.php, and "id" in posts.php.'}, {'type': 'list_item', 'content': 'Send HTTP GET requests with SQL injection payloads such as UNION SELECT statements to these parameters and observe if database information is returned.'}, {'type': 'list_item', 'content': 'Example commands using curl to test the parameters:'}, {'type': 'list_item', 'content': 'curl "http://target/search.php?search=\' UNION SELECT NULL, table_name FROM information_schema.tables-- "'}, {'type': 'list_item', 'content': 'curl "http://target/page.php?pageid=1 UNION SELECT schema_name, NULL FROM information_schema.schemata-- "'}, {'type': 'list_item', 'content': 'curl "http://target/posts.php?id=1 UNION SELECT user(), database(), version()-- "'}, {'type': 'paragraph', 'content': 'Successful injection will result in database metadata or other sensitive information being returned in the HTTP response, indicating the presence of the vulnerability.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include:'}, {'type': 'list_item', 'content': 'Apply input validation and sanitization on all user-supplied parameters, especially "search", "pageid", and "id".'}, {'type': 'list_item', 'content': 'Use prepared statements or parameterized queries to prevent SQL injection.'}, {'type': 'list_item', 'content': 'Restrict database user permissions to limit the impact of any potential injection.'}, {'type': 'list_item', 'content': 'If possible, update or patch the OOP CMS BLOG software to a version that addresses these vulnerabilities.'}, {'type': 'list_item', 'content': 'As a temporary measure, consider blocking or filtering suspicious requests targeting the vulnerable parameters at the web application firewall or network level.'}] [1, 2]