erusev/parsedown vulnerabilities

Parser for Markdown.

Registry
Composer
Latest
1.8.0
License
MIT

2 known advisories

The latest version, 1.8.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require erusev/parsedown:^1.8.0

Is your project on an affected erusev/parsedown?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for erusev/parsedown

  • MediumCVE-2018-1000162GHSA-qgpv-86r3-87fh30 Mar 2022

    Cross-site Scripting in Parsedown

    Affected
    <1.7.0
    Fixed in
    1.7.0
  • HighCVE-2019-10905GHSA-62m3-fc7f-jpp826 Mar 2022

    Parsedown Class-Name Injection

    Affected
    <1.7.2
    Fixed in
    1.7.2

Is your erusev/parsedown version vulnerable?

Which of your client projects still run an old erusev/parsedown?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.