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.0Is your project on an affected erusev/parsedown?
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
Cross-site Scripting in Parsedown
- Affected
- <1.7.0
- Fixed in
- 1.7.0
Parsedown Class-Name Injection
- Affected
- <1.7.2
- Fixed in
- 1.7.2
Is your erusev/parsedown version vulnerable?
- erusev/parsedown 1.8No known advisories in 1.8.0
- erusev/parsedown 1.7No known advisories in 1.7.4
- erusev/parsedown 1.62 advisories in 1.6.4
- erusev/parsedown 1.52 advisories in 1.5.4
- erusev/parsedown 1.42 advisories in 1.4.5
- erusev/parsedown 1.32 advisories in 1.3.0
- erusev/parsedown 0.92 advisories in 0.9.4
- erusev/parsedown 0.82 advisories in 0.8.3
- erusev/parsedown 0.72 advisories in 0.7.7
- erusev/parsedown 0.62 advisories in 0.6.0
- erusev/parsedown 0.52 advisories in 0.5.0
- erusev/parsedown 0.42 advisories in 0.4.8
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.