Skip to content

Product

Adobe robohelp server vulnerabilities

17 published CVES affecting Adobe robohelp server, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
17
Critical
0
High
8
Medium
9
Low
0
Unscored
0
CISA KEV
0

Latest Adobe robohelp server CVEs

Newest publication first

  1. HighCVSS 8.8 EPSS 1.5%

    RoboHelp Server earlier versions than RHS 11 Update 3 are affected by an Improper Authorization vulnerability which could lead to privilege escalation. An authenticated attacker could leverage this vulnerability to achieve full administrator privileges. Exploitation of this issue...

  2. HighCVSS 7.8 EPSS 39.4%

    Adobe Bridge 11.1.1 (and earlier) is affected by a stack overflow vulnerability due to insecure handling of a crafted file, potentially resulting in arbitrary code execution in the context of the current user. Exploitation requires user interaction in that a victim must open a cr...

  3. MediumCVSS 4.3 EPSS 1.7%

    Multiple cross-site scripting (XSS) vulnerabilities in RoboHelp 7 and 8, and RoboHelp Server 7 and 8, allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, related to (1) wf_status.htm and (2) wf_topicfs.htm in RoboHTML/WildFireExt/TemplateStock/.

  4. HighCVSS 9.3 EPSS 78.2% Framework module Public exploit

    Unrestricted file upload vulnerability in the RoboHelpServer Servlet (robohelp/server) in Adobe RoboHelp Server 8 allows remote attackers to execute arbitrary code by uploading a Java Archive (.jsp) file during a PUBLISH action, then accessing it via a direct request to the file...

  5. MediumCVSS 4.3 EPSS 13.8% Public exploit

    Cross-site scripting (XSS) vulnerability in Adobe RoboHelp X5, 6, and Server 6 allows remote attackers to inject arbitrary web script or HTML via a URL after a # (hash) in the URL path, as demonstrated using en/frameset-7.html, and possibly other unspecified vectors involving tem...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.