LuckyWP Table of Contents · Security record
Is LuckyWP Table of Contents safe?
No known vulnerability affects the current version (2.1.14). 6 issues were found in earlier versions and fixed, the latest disclosed on Apr 2, 2025.
Checked 3 days ago against the WPVulnerability database, for version 2.1.14.
How it’s looked after
- Last release
- Apr 16, 2025 (1 year ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.7.11 (current: 7.1)
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 90K+
6 known vulnerabilities
- 6 medium
None affects the current version.
Disclosed each year
- 20245
- 20251
Every known vulnerability in LuckyWP Table of Contents
Newest first, with any that affect the current version at the top.
Fixed in 2.1.11 · CVE-2025-2299 · Apr 2, 2025 · Wordfence
Fixed in 2.1.7 · CVE-2024-9641 · Nov 21, 2024 · Wordfence
- medium
Cross-site Scripting
Fixed in 2.1.6 · CVE-2024-2218 · Jun 14, 2024 · CVE
Fixed in 2.1.5 · CVE-2023-6487 · May 21, 2024 · Wordfence
Fixed in 2.1.5 · CVE-2024-2953 · May 21, 2024 · Wordfence
Fixed in 2.1.6 · CVE-2024-2119 · May 21, 2024 · Wordfence
Questions about LuckyWP Table of Contents’s security
Is LuckyWP Table of Contents safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep LuckyWP Table of Contents updated: most attacks target sites that haven’t updated.
Does LuckyWP Table of Contents have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 6 older issues, fixed in earlier versions, so keep LuckyWP Table of Contents up to date.
Is LuckyWP Table of Contents still maintained?
Its last release was 1 year ago, so it may no longer be actively maintained. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is LuckyWP Table of Contents compatible with the latest WordPress?
LuckyWP Table of Contents’s readme says it’s tested up to WordPress 6.7.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
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.