CVE-2019-25538
SQL Injection in 202CMS v10 Beta Allows Data Manipulation
Publication date: 2026-03-12
Last updated on: 2026-03-16
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| konradpl99 | 202cms | 10.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-2019-25538 is an SQL injection vulnerability found in 202CMS version 10 beta and earlier. It occurs because the application does not properly neutralize special characters in SQL commands, specifically in the "log_user" parameter.'}, {'type': 'paragraph', 'content': 'This flaw allows unauthenticated attackers to inject malicious SQL code through the log_user field, which can manipulate database queries.'}, {'type': 'paragraph', 'content': 'By exploiting this vulnerability, attackers can extract sensitive information from the database or modify its contents without authorization.'}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can have serious impacts because it allows attackers to access or alter sensitive database information without needing any privileges or user interaction.
- Attackers can extract confidential data from the database, potentially exposing personal or business-critical information.
- Attackers can modify database contents, which could lead to data corruption, unauthorized changes, or disruption of normal operations.
- Since the attack can be performed remotely over the network with low complexity and no authentication, it poses a high security risk.
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 sending crafted POST requests to the vulnerable parameters and observing the response times for time-based blind SQL injection indications.'}, {'type': 'paragraph', 'content': "Specifically, the 'log_user' parameter in index.php is vulnerable to blind SQL injection using time delays such as SLEEP(25) to confirm injection."}, {'type': 'paragraph', 'content': 'An example command to test this vulnerability using curl would be:'}, {'type': 'list_item', 'content': 'curl -X POST -d "log_user=1+%2b+((SELECT+1+FROM+(SELECT+SLEEP(25))A))" http://target/202cms10beta/index.php'}, {'type': 'paragraph', 'content': 'If the server response is delayed by approximately 25 seconds, it indicates the presence of the SQL injection vulnerability.'}] [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 the 'log_user' parameter to prevent SQL injection."}, {'type': 'list_item', 'content': 'Use prepared statements or parameterized queries in the application code to handle database queries safely.'}, {'type': 'list_item', 'content': 'Restrict access to the vulnerable endpoints if possible until a patch or update is applied.'}, {'type': 'list_item', 'content': "Monitor logs for suspicious requests targeting the 'log_user' parameter."}, {'type': 'paragraph', 'content': 'Since this vulnerability affects 202CMS version 10 beta and earlier, upgrading to a fixed or newer version when available is recommended.'}] [1, 2]