flarum/sticky vulnerabilities
Pin discussions to the top of the list.
- Registry
- Composer
- Latest
- 2.0.2
- License
- MIT
1 known advisory
The latest version, 2.0.2, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require flarum/sticky:^2.0.2Is your project on an affected flarum/sticky?
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 flarum/sticky
XSS in Flarum Sticky extension
- Affected
- >=0.1.0-beta.14 <0.1.0-beta.15.1
- Fixed in
- 0.1.0-beta.15.1
Is your flarum/sticky version vulnerable?
- flarum/sticky 2.0No known advisories in 2.0.2
- flarum/sticky 1.8No known advisories in 1.8.3
- flarum/sticky 1.7No known advisories in 1.7.0
- flarum/sticky 1.6No known advisories in 1.6.1
- flarum/sticky 1.5No known advisories in 1.5.0
- flarum/sticky 1.4No known advisories in 1.4.0
- flarum/sticky 1.3No known advisories in 1.3.0
Which of your client projects still run an old flarum/sticky?
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.