CVE-2023-47488
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 · uneditedCross Site Scripting vulnerability in Combodo iTop v.3.1.0-2-11973 allows a local attacker to obtain sensitive information via a crafted script to the attrib_manager_id parameter in the General Information page and the id parameter in the contact page.
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 confidenceCross Site Scripting (XSS) vulnerability in Combodo iTop v3.1.0-2-11973 affecting the attrib_manager_id parameter in the General Information page and the id parameter in the contact page. A local attacker can inject malicious scripts to execute in other users' browsers, potentially stealing session tokens, credentials, or other sensitive data.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify iTop version installedCheck the iTop version by accessing the web interface footer, or by locating the version file in the installation directory (such as version.php or similar version indicator file in the application's source files).Affected if The installed version is exactly 3.1.0-2-11973 (only this specific version is affected per the CVE).
-
Confirm General Information page is accessibleNavigate to the General Information page in the iTop web interface and locate any form or parameter that uses attrib_manager_id. This is typically found in admin or configuration sections where manager assignments are made.Affected if The page exists and the attrib_manager_id parameter is present and accepts user input.
-
Confirm Contact page is accessibleNavigate to the contact page in iTop and locate the id parameter in the URL or form. This page typically displays contact details and is accessed via URLs containing an id parameter.Affected if The page exists and the id parameter is present and accepts user input.
-
Inspect parameter reflection without encodingSubmit test values in the attrib_manager_id and id parameters (such as simple HTML like <script>alert(1)</script>) and observe if the values are rendered back in the page source without proper HTML encoding.Affected if The submitted values appear unencoded in the HTML output, indicating the vulnerability is present.
You are affected if your installed iTop version is exactly 3.1.0-2-11973 AND you have access to either the General Information page with attrib_manager_id or the contact page with the id parameter.
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 robust input validation and proper output encoding on both the attrib_manager_id and id parameters to prevent script injection. Apply context-appropriate sanitization (HTML encoding, URL encoding) when rendering these values in the General Information and contact pages.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47488 — 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-47488 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