GroupwareApplication · Horde

CVE-2020-8035

MEDIUM · 6.1 CVSS v3.1 Published 2020-05-18
Fix available
A fix is available. Upgrade to 5.2.22 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
The image view functionality in Horde Groupware Webmail Edition before 5.2.22 is affected by a stored Cross-Site Scripting (XSS) vulnerability via an SVG image upload containing a JavaScript payload. An attacker can obtain access to a victim's webmail account by making them visit a malicious URL.

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

A stored Cross-Site Scripting (XSS) vulnerability in Horde Groupware Webmail Edition's image view functionality allows attackers to upload SVG files containing embedded JavaScript payloads. When users view these malicious SVG images, the JavaScript executes in their browser context, enabling session hijacking and account takeover.

MitigationUpgrade to Horde Groupware Webmail Edition 5.2.22 or later, which implements proper sanitization of uploaded SVG files to strip or neutralize embedded JavaScript code.

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
GroupwareApplication
Affected:< 5.2.22

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

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

  1. Identify Horde Groupware installation
    Locate the Horde installation directory and check for the version file, typically found in the Horde root directory as version.php or in the documentation/config files. Check package.json, lib/version.php, or the admin interface for version information.
    Affected if Horde Groupware Webmail Edition is installed and the version is below 5.2.22
  2. Confirm image upload functionality is accessible
    Log into the Horde Webmail interface and navigate to the compose email or file attachment feature. Attempt to access the image/file upload functionality to verify it is enabled for users.
    Affected if The image upload and viewing functionality is enabled and accessible to users
  3. Verify SVG upload capability
    Attempt to upload an SVG file through the compose/attachment interface, or inspect the application's file type upload restrictions in the configuration settings under the file upload or attachment settings.
    Affected if SVG file uploads are permitted by the application configuration and not blocked at the server level
  4. Check if image viewing feature is active
    Navigate to an uploaded image or attachment and view it through the image viewer functionality. Confirm that SVG files render inline or through an img tag in the browser.
    Affected if SVG files render in the browser context through the image viewer, allowing script execution potential

A user is affected if Horde Groupware Webmail Edition version is below 5.2.22 AND the image/file upload and viewing functionality is enabled, as this combination allows stored XSS via malicious SVG uploads.

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 5.2.22 or later
Fixed in 5.2.22
Interim mitigation

Upgrade to Horde Groupware Webmail Edition 5.2.22 or later, which implements proper sanitization of uploaded SVG files to strip or neutralize embedded JavaScript code.

Fix this in Groupware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-8035 — 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-2020-8035 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