/

CVE-2026-30819

Severity:

HIGH RISK

(7.3)

Reflected XSS (CWE-79) in Combodo iTop Dashboard Function

CVE-2026-30819

Deferred

Vulnerability type

Category:

Cross-Site Scripting

CWE:

CWE-79

Impact:

Client-Side Code Execution and Session Compromise

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Combodo iTop contains a reflected Cross-Site Scripting vulnerability in the dashboard revert functionality, where the dashboard_id parameter is processed by /pages/ajax.render.php.

If an attacker can cause a victim to access a crafted request, injected script may execute in the victim's browser within the iTop application context.

Affected context

The issue occurs in iTop's web interface when the dashboard revert functionality handles the dashboard_id parameter through /pages/ajax.render.php. It becomes risky when attacker-controlled input is reflected into an HTTP response without sufficient output encoding, allowing a crafted link or request to target an authenticated user.

Exploit preconditions

  • Attack surface: iTop web application and its dashboard revert endpoint
  • Required access: The attacker generally needs to deliver a crafted URL or request to a user; direct application authentication may not be required to send the request, but a logged-in victim may be needed for meaningful impact
  • Trigger point: Processing of the dashboard_id parameter in /pages/ajax.render.php
  • Why exploitation is possible: Untrusted input may be reflected into a browser response without context-appropriate output encoding

Why this happens

The vulnerability results from reflected user input being incorporated into an HTTP response without adequate HTML or script-context encoding. When a browser interprets the reflected content as active markup or script, attacker-controlled code can run within the security context of the iTop application. 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 script in a victim's browser
  • Session information or accessible application data could be exposed
  • The attacker could perform actions using the victim's active application context
  • Administrative users could be targeted for broader account or workflow abuse
  • Users may be redirected to deceptive content or subjected to phishing within the application context

General mitigation guidance

Mitigation generally focuses on ensuring that all request parameters are treated as untrusted and safely encoded for their output context.

Common defensive patterns include:

  • Applying context-aware output encoding at every rendering sink
  • Validating dashboard_id against an allowlisted identifier format and expected resource set
  • Avoiding direct insertion of request values into HTML, JavaScript, or URL contexts
  • Using framework templating features that escape output by default
  • Applying a restrictive Content Security Policy as a defense-in-depth control
  • Limiting sensitive actions through authorization checks and anti-CSRF protections
  • Running application accounts with only the privileges required for their roles

How teams detect issues like this

Organizations can identify reflected XSS risks through:

  • Static analysis rules that trace request parameters into HTML, JavaScript, or URL rendering sinks
  • Code review checks for unescaped template interpolation and manual response construction
  • Dynamic testing of dashboard and AJAX endpoints with safely controlled special-character inputs
  • Web application firewall or gateway policies for suspicious script-bearing request patterns
  • Regression tests that verify output encoding and reject unexpected identifier formats

Automated security review tools may help identify data flows from request parameters to browser-rendered responses.

Sources

SourceLink
github.comgithub.com/Combodo/iTop/commit/104dd1970f3ad828896a5092b125edb4bc1340b6
github.comgithub.com/Combodo/iTop/security/advisories/GHSA-gccc-8mw3-hqhp

Frequently asked

questions

Yes, exploitation may be possible through a remotely delivered crafted request or link, provided that a victim accesses it and the affected endpoint reflects the supplied input.

Not necessarily. The key requirement is the ability to deliver the triggering request, although the impact may be greater when the victim is authenticated or has elevated privileges.

Treat dashboard_id and all other request values as untrusted, validate them against expected values, and apply context-aware output encoding before rendering them.

Use escaping-by-default templating, test all user-controlled input paths, enforce secure content policies, and include XSS-focused static and dynamic checks in the development lifecycle.

Find out what's already
exploitable in your codebase.