dbcve.org
ItopApplication · Combodo

CVE-2023-34444

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 2.7.9 / 3.0.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Combodo iTop is a simple, web based IT Service Management tool. When displaying pages/ajax.searchform.php XSS are possible for scripts outside of script tags. This issue has been fixed in versions 2.7.9, 3.0.4, 3.1.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a cross-site scripting (XSS) vulnerability in Combodo iTop's pages/ajax.searchform.php endpoint. The vulnerability allows attackers to inject malicious scripts outside of script tags, likely through unsanitized user input that gets rendered in the search form interface. This enables execution of arbitrary JavaScript in the context of other users' browsers.

MitigationUpgrade iTop to version 2.7.9, 3.0.4, or 3.1.0 which contain the fix. No workarounds are available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ItopApplication
Affected:< 2.7.9>= 3.0.0, < 3.0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the iTop installation directory
    Identify the webroot directory where Combodo iTop is installed. Check for the presence of the 'pages' subdirectory.
    Affected if The iTop installation directory and its pages subdirectory exist on the server.
  2. Confirm ajax.searchform.php exists
    Verify that the file pages/ajax.searchform.php is present in the iTop installation.
    Affected if The file pages/ajax.searchform.php exists in the iTop web directory.
  3. Determine installed iTop version
    Find and read the version information file or configuration within the iTop installation. Common locations include a version.php file, datamodel files, or the main configuration file.
    Affected if The installed version cannot be determined or is visible in the installation files.
  4. Compare version against affected ranges
    Match the identified version number to the vulnerable ranges: versions below 2.7.9, or versions 3.0.0 through 3.0.4.
    Affected if The installed version is less than 2.7.9, or is between 3.0.0 and 3.0.4 inclusive.
  5. Verify the search form feature is accessible
    Confirm that the ajax.searchform.php endpoint is accessible to users, typically through the iTop web interface or API.
    Affected if The endpoint can be reached via HTTP/HTTPS requests without authentication restrictions.

A user is affected if the ajax.searchform.php endpoint exists and the installed iTop version falls below 2.7.9 or between 3.0.0 and 3.0.4.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.9 / 3.0.4 or later
Fixed in 2.7.93.0.4
Interim mitigation

Upgrade iTop to version 2.7.9, 3.0.4, or 3.1.0 which contain the fix. No workarounds are available.

Recommended fix High confidence

Upgrade to iTop 2.7.9, 3.0.4, or 3.1.0 (latest stable release recommended)

  1. 1. Identify the currently installed iTop version by checking the version file or administration interface
  2. 2. For iTop versions < 2.7.9: Plan upgrade to version 2.7.9 or later (preferably latest 2.x LTS)
  3. 3. For iTop versions >= 3.0.0 and < 3.0.4: Plan upgrade to version 3.0.4 or later (preferably latest 3.x LTS, which is 3.1.0)
  4. 4. Backup the existing iTop database and files before upgrading
  5. 5. Download the appropriate fixed version from the official Combodo iTop download repository
  6. 6. Follow the official iTop upgrade documentation for your specific version migration path
  7. 7. Test the upgraded application to confirm the ajax.searchform.php XSS vulnerability is resolved
  8. 8. Verify that the application functions correctly post-upgrade
Caveat Review iTop release notes for breaking changes between your current version and target version before upgrading; major version jumps may require migration considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Itop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34444 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data