VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

php-horde: vulnerability history, versions and safety

php-horde is a package in the Debian ecosystem. Vulert records 14 vulnerabilities for it across 7 affected ranges, from Nov 2015 to May 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded U14
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all php-horde vulnerabilities

Vulert verdict on php-horde i

Updated on 23 Oct 2026

Careful: 2 of the 14 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 14 vulnerabilities on record across 4 years, none in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 14 over 4 years · 0 in the last year i
  • Latest disclosure 18 May 2020 i
  • Highest CVSS 8.8 i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 5.2.23+debian0-1 (exclusive) 2
up to 5.2.21+debian0-1 (exclusive) 2
up to 5.2.18+debian0-1 (exclusive) 2
up to 5.2.9+debian0-1 (exclusive) 2
up to 5.2.8+debian0-1 (exclusive) 2
up to 5.1.5+debian0-1 (exclusive) 2
all releases, no fix published yet 2

02 Disclosure history

How often vulnerabilities are recorded

  • 2015 2
  • 2016 2
  • 2017 2
  • 2019 6
  • 2020 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 14 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for php-horde

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CSRF Vulnerability in Horde Trean 8.8 high 5.2.21+debian0-1 24 Oct 2019
Cross-Site Scripting (XSS) Vulnerability in Horde Groupware (CVE-2016-2228) 6.1 medium 5.2.9+debian0-1 13 Apr 2016
XSS Vulnerability in Horde Groupware Webmail Edition 6.1 medium No fix published 24 Oct 2019
Stored XSS Vulnerability in Horde Groupware Webmail Edition (CVE-2020-8035) 6.1 medium 5.2.23+debian0-1 18 May 2020
XSS Vulnerability in Horde Groupware: php-horde and php-horde-core 5.4 medium 5.2.18+debian0-1 20 Nov 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About php-horde

Is php-horde safe to use?

Vulert records 14 vulnerabilities for php-horde in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 14 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does php-horde have?

14 vulnerabilities are recorded for php-horde in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 14 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new php-horde vulnerabilities disclosed?

0 vulnerabilities were recorded for php-horde in the last 12 months, and the oldest entry in this database dates to 19 Nov 2015. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of php-horde are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor php-horde for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the php-horde version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.