CVE-2018-10231
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 (XSS) vulnerability in TOPdesk before 8.05.017 (June 2018 version) and before 5.7.SR9 allows remote attackers to inject arbitrary web script or HTML via unspecified parameters.
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 confidenceStored cross-site scripting (XSS) vulnerability in TOPdesk service management software allows remote attackers to inject arbitrary JavaScript or HTML through unspecified parameters. The malicious payload is stored and executed when other users access the affected functionality, potentially leading to session hijacking or credential theft.
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< 8.05.017< 5.7.sr9CVSS 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.0/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.
-
Identify installed TOPdesk versionLog into the TOPdesk administrator portal and navigate to About TOPdesk or System > Database > Version information. Alternatively, check the software release notes or installer metadata on the server.Affected if The version shown is below 8.05.017 or below 5.7.sr9 (for the respective product lines)
-
Confirm TOPdesk product lineDetermine whether your installation is Topdesk Topdesk (newer branch) or an older 5.x release. This distinction matters because the version thresholds differ: < 8.05.017 for the main product, or < 5.7.sr9 for the 5.x branch.Affected if Running either product line at a version below its respective threshold
-
Review TOPdesk audit logs for script injection patternsAccess the TOPdesk audit or operation logs (typically via System > Logging or the database logs). Search for entries containing HTML tags such as <script>, <img onerror=, javascript:, or other suspicious JavaScript event handlers in fields that accept user input.Affected if Any audit log entries contain encoded or raw XSS payloads in operator-created fields
-
Inspect database for stored XSS payloadsQuery the TOPdesk database tables that store operator input (such as person notes, incident descriptions, or asset fields) for patterns like <script, onerror=, onload=, javascript:, or hexadecimal/obfuscated script variants.Affected if Database records contain persisted malicious scripts that were not authored by legitimate administrators
-
Examine web server access logs for XSS attempt indicatorsReview the web server logs (IIS, Apache, or Tomcat depending on TOPdesk deployment) for incoming requests with XSS payloads in parameters. Look for unusual query strings or form submissions containing script tags.Affected if Logs show repeated XSS injection attempts against TOPdesk input fields, indicating active targeting
You are affected if your TOPdesk installation version is below 8.05.017 (newer branch) or below 5.7.sr9 (5.x branch), and you find stored XSS payloads in logs, database, or audit trails.
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 data5.7.sr98.05.017
Update TOPdesk to version 8.05.017 (June 2018) or later, or 5.7.SR9 or later. Apply input validation and output encoding as compensating controls until patching is completed.
- 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-2018-10231 — 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-2018-10231 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