CVE-2018-25210
SQL Injection in WebOfisi E-Ticaret 'urun' Parameter Allows Data Manipulation
Publication date: 2026-03-26
Last updated on: 2026-03-27
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| web-ofisi | e-ticaret | to 4.0.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability can have serious security impacts including unauthorized access to the backend database, data leakage, and manipulation of database contents.
Attackers can exploit the SQL injection to extract sensitive information, execute arbitrary SQL commands, and disrupt the integrity of the data.
The presence of an XSS vulnerability in the same parameter also allows attackers to inject malicious scripts, potentially compromising users' browsers and stealing session information.
Can you explain this vulnerability to me?
CVE-2018-25210 is an SQL injection vulnerability in WebOfisi E-Ticaret version 4.0. It exists in the 'urun' GET parameter of a specific endpoint, allowing unauthenticated attackers to manipulate backend database queries.
Attackers can inject SQL payloads through this parameter to perform various types of SQL injection attacks, including boolean-based blind, error-based, time-based blind, and stacked query attacks. This enables them to execute unauthorized database queries and potentially extract sensitive information.
Additionally, the same 'urun' parameter is vulnerable to Cross-Site Scripting (XSS), allowing injection of malicious JavaScript code.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in the 'urun' GET parameter can be detected by sending crafted HTTP requests to the vulnerable endpoint and observing the responses for signs of SQL injection.
- Use boolean-based blind SQL injection payloads such as: kategori=20&urun=test") RLIKE (SELECT (CASE WHEN (6525=6525) THEN 0x74656474 ELSE 0x28 END)) AND ("YWLa"="YWLa
- Use error-based SQL injection payloads like: kategori=20&urun=test") OR (SELECT 6556 FROM(SELECT COUNT(*),CONCAT(0x71626b6b71,(SELECT(ELT(6556=6556,1))),0x716b716b71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND ("ExaV"="ExaV
- For MySQL versions below 5.0.12, test stacked queries with payloads such as: kategori=20&urun=test");SELECT BENCHMARK(5000000,MD5(0x44527964)) AND ("KGaO"="KGaO
- For MySQL 5.0.12 and above, use time-based blind SQL injection payloads like: kategori=20&urun=test") OR SLEEP(5) AND ("sDnb"="sDnb
These payloads can be sent using tools like curl, Burp Suite, or sqlmap to detect the vulnerability by analyzing the server's response or delay.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs, especially the 'urun' GET parameter, to prevent SQL injection.
Use prepared statements (parameterized queries) in the backend code to safely handle database queries.
Apply web application firewall (WAF) rules to detect and block malicious SQL injection attempts targeting the vulnerable parameter.
If possible, update or patch the WebOfisi E-Ticaret application to a version where this vulnerability is fixed.
Monitor logs for suspicious requests containing SQL injection payloads and respond accordingly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in WebOfisi E-Ticaret 4.0 allows unauthenticated attackers to manipulate database queries and potentially extract sensitive information. Such unauthorized access and data exposure can lead to non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive data against unauthorized access and breaches.
Because attackers can execute arbitrary SQL commands and extract confidential data, this vulnerability poses a significant risk to the confidentiality and integrity of stored data, which are core requirements under these regulations.
Therefore, if exploited, this vulnerability could result in violations of compliance requirements related to data security, privacy, and breach notification obligations.