VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

php-horde-css-parser: vulnerability history, versions and safety

php-horde-css-parser is a package in the Debian ecosystem. Vulert records 3 vulnerabilities for it across 1 release, from Jun 2020 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded U3
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-css-parser vulnerabilities

Vulert verdict on php-horde-css-parser i

Updated on 23 Oct 2026

Careful: 2 of the 3 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 3 vulnerabilities on record across 5 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 3 over 5 years · 0 in the last year i
  • Latest disclosure 14 Oct 2025 i
  • Highest CVSS 9.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

Every version Vulert holds for php-horde-css-parser, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.0.11-8 U3 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for php-horde-css-parser

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Remote Code Execution Risk in php-horde-css-parser Due to Uncontrolled Data Evaluation 9.8 critical No fix published 03 Jun 2020
Remote Code Execution Risk in php-horde-css-parser Package Due to Uncontrolled Data Evaluation N/A unrated No fix published 03 Jun 2020
Critical Security Update for php-horde-css-parser: CVE-2020-13756 N/A unrated 1.0.11-8+deb11u1 14 Oct 2025

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-css-parser

Is php-horde-css-parser safe to use?

Vulert records 3 vulnerabilities for php-horde-css-parser in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 3 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-css-parser have?

3 vulnerabilities are recorded for php-horde-css-parser in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 3 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-css-parser vulnerabilities disclosed?

0 vulnerabilities were recorded for php-horde-css-parser in the last 12 months, and the oldest entry in this database dates to 03 Jun 2020. 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-css-parser 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-css-parser for upcoming vulnerabilities?

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