Robohelp ServerApplication · Adobe

CVE-2021-28588

HIGH · 8.8 CVSS v3.1 Published 2021-06-28
Fix available
A fix is available. Upgrade to after 2019.0.9 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Server version 2019.0.9 (and earlier) is affected by a Path Traversal vulnerability when parsing a crafted HTTP POST request. An authenticated attacker could leverage this vulnerability to achieve arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction.

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 · high confidence

Adobe RoboHelp Server 2019.0.9 and earlier contains a path traversal vulnerability that allows authenticated attackers to craft malicious HTTP POST requests with directory traversal sequences (e.g., ../../../') to write files outside the intended directory, achieving arbitrary code execution in the context of the web server user.

MitigationUpgrade to a patched version of Adobe RoboHelp Server (2020.x or later) that addresses this vulnerability. Additionally, enforce strict authentication controls and consider network segmentation to limit exposure of the RoboHelp Server administration interfaces.

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
Robohelp ServerApplication
Affected:<= 2019.0.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify Adobe RoboHelp Server installation
    Locate the RoboHelp Server installation directory and check for version files or use system inventory tools to identify if Adobe RoboHelp Server is installed
    Affected if Adobe RoboHelp Server is found with version 2019.0.9 or earlier
  2. Verify installed version against affected range
    Check the installed version number - look in the application installation folder for version information or check system registry if on Windows
    Affected if The installed version is 2019.0.9 or any earlier version (2019.x through initial releases)
  3. Assess network exposure of admin interface
    Determine if the RoboHelp Server web administration interface is accessible from the network or internet without VPN or firewall restrictions
    Affected if The admin interface is exposed to untrusted networks
  4. Review web server write locations
    Examine the web server document root and related directories for unexpected files, particularly script files (.asp, .jsp, .php, .exe) that were not intentionally deployed
    Affected if Arbitrary or unexpected files exist outside the intended upload directories, especially in web-accessible locations

A user is affected if Adobe RoboHelp Server version 2019.0.9 or earlier is installed and the server admin interface is network-accessible, as authenticated attackers could exploit the path traversal to write malicious files.

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 a release after 2019.0.9
Interim mitigation

Upgrade to a patched version of Adobe RoboHelp Server (2020.x or later) that addresses this vulnerability. Additionally, enforce strict authentication controls and consider network segmentation to limit exposure of the RoboHelp Server administration interfaces.

Fix this in Robohelp Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-28588 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-28588 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