Summary
Chanjet CRM contains an unauthenticated SQL injection vulnerability in a webservice endpoint that processes the site_id GET parameter without adequate input handling. A remote attacker may manipulate this parameter to execute database queries and retrieve sensitive information when the endpoint is reachable.
Affected context
The vulnerability occurs in Chanjet CRM deployments where the webservice endpoint is exposed over a network and accepts the site_id GET parameter. Risk is higher when the endpoint is reachable without authentication and the associated database account has broad query privileges.
Exploit preconditions
- Attack surface: Network-accessible Chanjet CRM webservice endpoint
- Required access: No authentication may be required when the endpoint is exposed
- Trigger point: Processing of the
site_idGET parameter - Why exploitation is possible: User-controlled input may reach database query construction without sufficient parameterization or sanitization
Why this happens
The underlying bug is the use of untrusted request data in database queries without consistently binding it as a parameter. This permits SQL syntax supplied through the site_id value to alter query behavior, including UNION-based query manipulation. The issue maps to CWE-89, SQL Injection, because external input is interpreted as database command structure rather than treated solely as data.
Potential impact
- An attacker may retrieve sensitive records from the underlying database.
- An attacker could infer database structure and exposed application data.
- Database contents may be modified if the vulnerable query context permits write operations.
- The vulnerability can contribute to unauthorized access to connected application functions.
General mitigation guidance
Mitigation generally focuses on removing executable query structure from
externally supplied values.
Common defensive patterns include:
- Use parameterized queries or prepared statements for all database operations.
- Apply allowlist validation for identifiers and values such as site IDs.
- Avoid constructing SQL statements through string concatenation.
- Use a database account with only the privileges required by the application.
- Limit network exposure of administrative and webservice endpoints.
- Add centralized input validation and consistent error handling without exposing database details.
How teams detect issues like this
Organizations can look for:
- Static-analysis findings involving request parameters concatenated into SQL statements.
- Code-review signals such as dynamic query construction and missing parameter binding.
- Web application logs containing unexpected SQL operators, UNION patterns, or repeated parameter probing.
- Database audit events showing anomalous queries from the CRM service account.
- Policy enforcement requiring parameterized database access and security testing for externally reachable endpoints.
Automated code and dependency review tools may help identify these patterns during development.

