S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Mar 27, 2025

CNVD-2018-06472 Scanner

CNVD-2018-06472 Scanner - SQL Injection vulnerability in Cobub Razor

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.4k
Times Used
continuous scan runs
3.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
Detail

Cobub Razor is an open-source mobile application analytics system widely used for tracking user behavior and statistics on mobile applications. The primary purpose of this tool is to provide detailed multi-dimensional reports to users. Developed by Western Bridge, it is used by developers and analysts to gain insights into application performance.

The SQL injection vulnerability in Cobub Razor allows remote attackers to manipulate database queries by exploiting the 'channel_name' parameter. Such vulnerabilities can be detrimental to applications as they may lead to unintended database operations. Given the severity, it's crucial for users to address this vulnerability promptly.

The vulnerability specifically affects the endpoint '/index.php?/manage/channel/addchannel', where the 'channel_name' parameter is vulnerable to injection attacks. Malicious inputs can be embedded in SQL commands, allowing unauthorized access or modification of database content. The system fails to sanitize inputs properly, rendering it susceptible to this flaw.

When exploited, an attacker could potentially access sensitive information, compromise data integrity, or completely disrupt application services. Unauthorized users could extract data or perform actions without permissions, potentially leading to severe data breaches.

REFERENCES

Solution Advice
  • Update Cobub Razor to the latest patch or version available from the official website.
  • Implement prepared statements and parameterized queries to prevent SQL injection.
  • Ensure that special characters are escaped or encoded before entering the database.
  • Validate the data type for each input, ensuring numeric fields are strictly numbers.
  • Use consistent encoding like UTF-8 throughout the system to avoid bypassing filters.
  • Restrict database access and permissions to minimize the impact of potential attacks.
  • Hide SQL error messages to prevent attackers from gathering intelligence from errors.
  • Filter potentially harmful SQL keywords using regular expressions to disrupt injection attempts.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.