Scrollsequence · Security record
Is Scrollsequence safe?
No known vulnerability affects the current version (1.6.3). 5 issues were found in earlier versions and fixed, the latest disclosed on Mar 16, 2024.
Checked 3 days ago against the WPVulnerability database, for version 1.6.3.
How it’s looked after
- Last release
- Jun 7, 2026 (5 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 7.0.8
- Support resolved
- 1 of 1 threads in two months
- Active installs
- 3K+
5 known vulnerabilities
- 1 high
- 2 medium
- 2 not rated
None affects the current version.
Disclosed each year
- 20223
- 20231
- 20241
Every known vulnerability in Scrollsequence
Newest first, with any that affect the current version at the top.
Fixed in 1.5.5 · CVE-2024-29118 · Mar 16, 2024 · Wordfence
Fixed in 1.4.0 · CVE-2023-33999 · Jul 18, 2023 · WPScan
Fixed in 1.2.4 · CVE-2022-4974 · Mar 4, 2022 · Wordfence
Fixed in 1.2.4 · Feb 28, 2022 · Patchstack
Fixed in 1.2.4 · Feb 28, 2022 · Patchstack
Questions about Scrollsequence’s security
Is Scrollsequence safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Scrollsequence updated: most attacks target sites that haven’t updated.
Does Scrollsequence have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 5 older issues, fixed in earlier versions, so keep Scrollsequence up to date.
Is Scrollsequence still maintained?
Yes. Its last release was 5 months ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is Scrollsequence compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.