VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

austintoddj/canvas: vulnerability history, versions and safety

austintoddj/canvas is a package in the Packagist ecosystem. Vulert records 2 vulnerabilities for it across 46 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
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 austintoddj/canvas vulnerabilities

Vulert verdict on austintoddj/canvas i

Updated on 23 Oct 2026

Careful: 2 of the 2 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 2 vulnerabilities on record across 1 year, 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 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 5.4 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 austintoddj/canvas, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for austintoddj/canvas

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000507: Canvs Canvas XSS Vulnerability 5.4 medium No fix published 14 May 2022
CVE-2017-8298: Cross-site Scripting (XSS) in austintoddj/canvas 5.4 medium No fix published 17 May 2022

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 austintoddj/canvas

Is austintoddj/canvas safe to use?

Vulert records 2 vulnerabilities for austintoddj/canvas in Packagist: 0 critical, 0 high, 2 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does austintoddj/canvas have?

2 vulnerabilities are recorded for austintoddj/canvas in the Packagist ecosystem: 0 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new austintoddj/canvas vulnerabilities disclosed?

0 vulnerabilities were recorded for austintoddj/canvas in the last 12 months, and the oldest entry in this database dates to 14 May 2022. 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 austintoddj/canvas 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 austintoddj/canvas for upcoming vulnerabilities?

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