CVE Intelligence
Skip to main content
MEDIUMpublic exploit

CVE-2020-8866

CVE-2020-8866 Vulnerability Analysis & Exploit Intelligence

This vulnerability allows remote attackers to create arbitrary files on affected installations of Horde Groupware Webmail Edition 5.2.22. Authentication is required to exploit this vulnerability. The specific flaw exists within add.php. The issue results from the lack of proper validation of user-supplied data, which can allow the upload of arbitrary files. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of the www-data user. Was ZDI-CAN-10125.

Published Updated Sources: cvelistV5, zdi

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

10%

chance of exploitation in 30 days

Affects

horde

groupware_webmail_edition

CVSS base

4.3

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

horde

Products (1)

groupware webmail edition

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4.3CVSS 3.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-434

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

exploit db

References

3 on the record

Elsewhere on this site

  • hordeevery CVE for this vendor
  • CWE-434other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.