dbcve.org
RobohelpApplication · Adobe

CVE-2017-3104

MEDIUM · 6.1 CVSS v3.0 Published 2017-12-01
Fix available
A fix is available. Upgrade to 12.0.4.460 / 2017.0.1 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
Adobe RoboHelp has a cross-site scripting (XSS) vulnerability. This affects versions before RH12.0.4.460 and RH2017 before RH2017.0.2.

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 confidence

Adobe RoboHelp versions before RH12.0.4.460 and RH2017 before RH2017.0.2 contain a cross-site scripting (XSS) vulnerability that could allow attackers to inject malicious scripts through the application.

MitigationUpdate Adobe RoboHelp to version RH12.0.4.460 or RH2017.0.2 or later to remediate this vulnerability.

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
RobohelpApplication
Affected:< 2017.0.1< 12.0.4.460

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.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 checks

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

  1. Verify Adobe RoboHelp installation
    Check for Adobe RoboHelp in the Windows Start Menu, or look in Control Panel > Programs and Features for an entry named 'Adobe RoboHelp'
    Affected if Adobe RoboHelp is listed as an installed program
  2. Locate the installed version number
    In Programs and Features, find the Adobe RoboHelp entry and note the version number shown (typically in the 'Version' column); alternatively, launch RoboHelp and go to Help > About Adobe RoboHelp to view the exact version
    Affected if Version displayed is below 12.0.4.460 for the RH12.x product line, or below 2017.0.2 for the RH2017 product line
  3. Identify the product version family
    Determine whether the installation is the RH12.x legacy version or the RH2017 version by examining the version number format - RH12.x versions start with 12, while RH2017 versions start with 2017
    Affected if The version family is either RH12.x or RH2017 and falls below the safe version thresholds

You are affected if Adobe RoboHelp is installed and the version is either 2017.x below 2017.0.2, or 12.x below 12.0.4.460.

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.

From vendor data
Upgrade available Upgrade to 12.0.4.460 / 2017.0.1 or later
Fixed in 12.0.4.4602017.0.1
Interim mitigation

Update Adobe RoboHelp to version RH12.0.4.460 or RH2017.0.2 or later to remediate this vulnerability.

Fix this in Robohelp 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-2017-3104 — 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-2017-3104 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