CVE-2019-25539
Received Received - Intake
Blind SQL Injection in 202CMS v10 Beta Allows Data Extraction

Publication date: 2026-03-12

Last updated on: 2026-03-16

Assigner: VulnCheck

Description
202CMS v10 beta contains a blind SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the log_user parameter. Attackers can send POST requests to index.php with crafted SQL payloads using time-based blind injection techniques to extract sensitive database information.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-12
Last Modified
2026-03-16
Generated
2026-06-16
AI Q&A
2026-03-12
EPSS Evaluated
2026-06-15
NVD
CVE-2019-25539
EUVD
EUVD-2019-19827
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
konradpl99 202cms 10.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

[{'type': 'paragraph', 'content': 'CVE-2019-25539 is a blind SQL injection vulnerability found in 202CMS version 10 beta and earlier. It occurs in the register.php script through the "log_user" parameter. This flaw allows unauthenticated attackers to inject malicious SQL code by sending specially crafted POST requests to index.php. The attack uses time-based blind SQL injection techniques to manipulate database queries and extract sensitive information from the backend database.'}] [1]

Impact Analysis

This vulnerability can have a significant impact as it allows attackers to extract sensitive information from the database without any authentication. Since the attack can be performed remotely over the network with low complexity and no user interaction, it poses a high risk of data exposure. The confidentiality of the database is highly compromised, although the impact on data integrity is low and there is no impact on availability.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by sending crafted POST requests to the index.php script targeting the log_user parameter with time-based blind SQL injection payloads. Monitoring for unusual POST requests containing SQL injection patterns in the log_user parameter can help identify exploitation attempts.'}, {'type': 'paragraph', 'content': 'A possible command to test for this vulnerability using curl might be:'}, {'type': 'list_item', 'content': 'curl -X POST -d "log_user=1\' AND IF(SLEEP(5),1,0)-- -" http://targetsite/index.php'}, {'type': 'paragraph', 'content': 'If the response is delayed by the sleep time (e.g., 5 seconds), it indicates a time-based blind SQL injection vulnerability.'}] [1]

Mitigation Strategies

Immediate mitigation steps include:

  • Apply input validation and sanitization on the log_user parameter to prevent SQL injection.
  • Use prepared statements or parameterized queries in the affected register.php and index.php scripts.
  • Restrict access to the vulnerable scripts if possible until a patch is applied.
  • Monitor web server logs for suspicious POST requests targeting the log_user parameter.

Additionally, check for and apply any available patches or updates from the vendor to fix the vulnerability.

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