HomeWordPress vulnerabilitiesLuckyWP Table of Contents
LuckyWP Table of Contents vulnerabilities
LuckyWP Table of Contents has 6 known vulnerabilities in this database. The most recent published record is dated 3 Apr 2025.
- Known vulnerabilities
- 6
- Active installs
- 100,000+
- Latest version
- 2.1.14
- Last updated
- 16 Apr 2025
- Most recent
- 3 Apr 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2025-2299 | Medium 6.1 | Before 2.1.11 | Fixed in 2.1.11 | 3 Apr 2025 |
| Cross-site scripting (XSS) CVE-2024-9641 | Medium 4.8 | Before 2.1.7 | Fixed in 2.1.7 | 12 Dec 2024 |
| Cross-site scripting (XSS) CVE-2024-2218 | Medium 4.6 | Before 2.1.6 | Fixed in 2.1.6 | 14 Jun 2024 |
| Cross-site scripting (XSS) CVE-2024-2119 | Medium 6.1 | Before 2.1.5 | Fixed in 2.1.5 | 22 May 2024 |
| Cross-site scripting (XSS) CVE-2024-2953 | Medium 5.5 | Before 2.1.5 | Fixed in 2.1.5 | 22 May 2024 |
| Cross-site scripting (XSS) CVE-2023-6487 | Medium 4.4 | Before 2.1.5 | Fixed in 2.1.5 | 22 May 2024 |
Read the published descriptions
- CVE-2025-2299, 3 Apr 2025
- The LuckyWP Table of Contents plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.10. This is due to missing or incorrect nonce validation on the 'ajaxEdit' function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2024-9641, 12 Dec 2024
- The LuckyWP Table of Contents WordPress plugin before 2.1.7 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2024-2218, 14 Jun 2024
- The LuckyWP Table of Contents WordPress plugin through 2.1.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2024-2119, 22 May 2024
- The LuckyWP Table of Contents plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the attrs parameter in all versions up to, and including, 2.1.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2024-2953, 22 May 2024
- The LuckyWP Table of Contents plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple parameters in versions up to, and including, 2.1.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with Contributor permissions and above to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-6487, 22 May 2024
- The LuckyWP Table of Contents plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘Header Title' field in all versions up to and including 2.1.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. CVE-2024-2218 appears to be a duplicate of this issue. CVE record
What to do if you run LuckyWP Table of Contents
If you run LuckyWP Table of Contents, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new LuckyWP Table of Contents vulnerabilities
Free. We email you when a new vulnerability is published for LuckyWP Table of Contents, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.