Is spatie/schema-org 4.0 vulnerable?
Composer · 3 releases from 4.0.0 to 4.0.2 · latest spatie/schema-org is 5.0.2 · checked 18 Nov 2026
No known advisories in the last release
spatie/schema-org 4.0.2, the last 4.0 release, has no known advisories. 1 advisory affects earlier 4.0.x releases, so update to 4.0.2.
composer require spatie/schema-org:^4.0.2Is your project on an affected spatie/schema-org?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 4.0.x, affecting earlier releases
Schema.org has cross-site scripting (XSS) via script break-out in toScript() output
- Affected
- >=3.23.1 <3.23.2 · >=4.0.0 <4.0.2
- Fixed in
- 3.23.2, 4.0.2
Every spatie/schema-org 4.0.x release
Affected: 4.0.0 to 4.0.1. 4.0.2 is not affected. Latest spatie/schema-org: 5.0.2.
| Version | Known advisories |
|---|---|
| spatie/schema-org 4.0.2 | None |
| spatie/schema-org 4.0.1 | GHSA-hwmc-r6mf-jh83 |
| spatie/schema-org 4.0.0 | GHSA-hwmc-r6mf-jh83 |
Which of your client projects are still on spatie/schema-org 4.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact spatie/schema-org version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other spatie/schema-org versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.