Summary
Combodo iTop contains a reflected cross-site scripting vulnerability in its testing functionality for OQL queries. An attacker may be able to execute script in a victim's browser when crafted input is reflected into a response without appropriate output encoding, particularly when a victim follows a malicious link or views attacker-controlled content.
Affected context
The issue occurs in iTop deployments that expose the testing interface for OQL queries and reflect query-related input into web responses. Risk depends on whether an attacker can cause a privileged or otherwise relevant user to access a crafted request, and whether browser-side security controls limit script execution or access to application data.
Exploit preconditions
- Attack surface: Web-based OQL query testing functionality
- Required access: Typically, the ability to submit or influence OQL test input; victim interaction may also be required
- Trigger point: Rendering a response that includes attacker-controlled input
- Why exploitation is possible: Input is reflected into an HTML or script-relevant context without sufficient context-aware output encoding
Why this happens
The vulnerability is caused by treating user-controlled query or request data as safe for direct inclusion in a web response. When output is not encoded for its specific browser context, the browser may interpret the reflected value as markup or script rather than ordinary text. This behavior maps to CWE-79, Improper Neutralization of Input During Web Page Generation, commonly known as cross-site scripting.
Potential impact
- An attacker may execute JavaScript in a victim's browser context
- Session information or accessible application data could be exposed
- Account actions could be performed using the victim's privileges
- Users may be redirected to deceptive content or subjected to phishing
- Administrative workflows or displayed IT service data could be altered
General mitigation guidance
Mitigation generally centers on applying context-aware output encoding at every response boundary and treating query input as untrusted data. Secure patterns include using templating systems with automatic escaping, avoiding unsafe HTML construction, validating inputs against the expected OQL grammar, and applying a restrictive content security policy where practical. Sensitive operations should require appropriate authorization and least privilege, while session protections and reduced client-side data exposure can limit impact if script execution occurs.
How teams detect issues like this
Detection approaches include static analysis for string concatenation or interpolation of request parameters into HTML, JavaScript, or attribute contexts; code review checks for missing context-aware encoding; and dynamic security testing of OQL testing responses using harmless marker values. Organizations can also enforce secure templating and output-encoding policies in CI, while browser security headers and web application monitoring may help identify suspicious reflected-input activity.

