Security readout for executives and security teams
Plain-English summary
Combodo iTop had a CSRF weakness that could let an attacker trick a user into performing unintended state-changing actions. It requires user interaction, but the integrity impact is high because iTop often manages IT service operations. Fixed versions are 2.7.6 and 3.0.0.
Executive priority
Schedule remediation in the normal vulnerability cycle, faster for internet-accessible or high-privilege iTop environments. This is not marked as known exploited in the supplied sources, but the business risk is meaningful because successful abuse could alter IT service-management data or workflows.
Technical view
CVE-2021-41245 is CWE-352 in Combodo iTop. CSRF tokens generated by privUITransactionFile were not properly checked in versions before the fixed releases, allowing forged cross-site requests when a victim interacts with attacker-controlled content. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges required, user interaction required, high integrity impact.
Likely exposure
Organizations running Combodo iTop versions earlier than 2.7.6, or pre-fixed 3.0.0 builds, are potentially exposed. Exposure is most relevant where iTop is reachable by users through a browser and authenticated users can perform sensitive operational changes.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue requires user interaction, consistent with CSRF. Public advisory and bounty references exist, so vulnerability managers should treat it as publicly known rather than theoretical.
Researcher notes
Focus validation on affected iTop versions and the CSRF token handling around privUITransactionFile. Do not assume broader products or modules are affected beyond the cited Combodo iTop issue. Evidence supports fixed versions and a configuration workaround, but does not establish active exploitation.
Mitigation direction
- Upgrade Combodo iTop to 2.7.6, 3.0.0, or a later fixed release.
- If immediate upgrade is blocked, apply the vendor workaround using session implementation in iTop configuration.
- Review Combodo’s advisory before changing production configuration.
- Prioritize externally reachable or broadly accessible iTop deployments first.
Validation and detection
- Inventory all Combodo iTop instances and record exact versions.
- Confirm each instance runs 2.7.6, 3.0.0, or a later fixed version.
- Check whether the vendor session-based workaround is configured where upgrades are pending.
- Review change-management records for sensitive iTop actions during the exposure window.
- Use vendor references to confirm the privUITransactionFile token-check fix is present.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-41245 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Combodo/iTop/security/advisories/GHSA-33pr-5776-9jqfCVE reference · x_refsource_CONFIRM
- https://github.com/Combodo/iTop/commit/7757f1f2d2330d49a3ebb40194f5ec4c8eaf8186CVE reference · x_refsource_MISC
- https://huntr.dev/bounties/0a39630d-f4b9-4468-86d8-aea3b02f91aeCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.