CVE-2023-47489
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 · uneditedCSV injection in export as csv in Combodo iTop v.3.1.0-2-11973 allows a local attacker to execute arbitrary code via a crafted script to the export-v2.php and ajax.render.php components.
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 · moderate confidenceCSV injection vulnerability in Combodo iTop's export functionality (export-v2.php and ajax.render.php) allows a local attacker to inject malicious formulas into CSV exports. When opened in spreadsheet applications, these crafted formulas can execute arbitrary code on the victim's system.
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= 3.1.0-2-11973CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify iTop installation and versionLocate the iTop installation directory and check the version file (typically version.php or similar file containing the version string). Compare the installed version to the affected version 3.1.0-2 build 11973.Affected if The installed iTop version is 3.1.0-2 build 11973 or lower.
-
Confirm export-v2.php existsCheck if the file export-v2.php exists in the web root or application directory of the iTop installation.Affected if The file export-v2.php is present and accessible on the server.
-
Confirm ajax.render.php existsCheck if the file ajax.render.php exists in the iTop application directory.Affected if The file ajax.render.php is present and accessible on the server.
-
Verify CSV export functionality is enabledAccess the iTop web interface and attempt to use the export feature (typically found in the Data Administration or Export menu). Check if users with appropriate permissions can generate CSV exports.Affected if The CSV export functionality is enabled and accessible to users.
-
Test for formula injection character handlingCreate a test object in iTop with a field containing a formula injection character (=, +, -, @, tab, or CR) followed by text (e.g., '=CMD|'). Export that object to CSV and examine the raw CSV content to see if the character is escaped or stripped.Affected if The formula injection characters are NOT escaped or stripped in the CSV export output (raw CSV shows unescaped =, +, -, @, or similar characters).
A user is affected if they are running Combodo iTop version 3.1.0-2 build 11973 or lower AND have the CSV export functionality enabled, with unescaped formula injection characters appearing in exported CSV files.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement input sanitization to escape or strip formula injection characters (=, +, -, @, tab, CR) from user-supplied data before including it in CSV exports. Consider disabling macro execution in generated CSV files or using proper content-type headers.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47489 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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