LuckyWP Table of Contents <= 2.1.10 - Cross-Site Request Forgery to Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1.11
- Affected Plugin
- LuckyWP Table of Contents
- Affected Version
<= 2.1.10- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2025-2299
At a glance
CVE-2025-2299 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the LuckyWP Table of Contents WordPress plugin, affecting versions <= 2.1.10. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.11; sites on affected versions should update now. Disclosed April 2025, reported by mikemyers.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
LuckyWP Table of Contents <= 2.1.10 carries this weakness at ajaxEdit, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For LuckyWP Table of Contents the fix is 2.1.11: builds <= 2.1.10 are affected, anything from 2.1.11 onward is not.
Remediation
Update to version 2.1.11, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to LuckyWP Table of Contents: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: LuckyWP Table of Contents 2.1.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.1CVE-2024-2119: LuckyWP Table of Contents <= 2.1.5 Reflected XSS
CVE-2024-2119 - 5.5CVE-2024-2953: LuckyWP Table of Contents <= 2.1.4 Stored XSS
CVE-2024-2953 - 4.4CVE-2024-9641: LuckyWP Table of Contents <= 2.1.6 Stored XSS
CVE-2024-9641 - 4.4CVE-2023-6487: LuckyWP Table of Contents <= 2.1.5 Cross-Site Scripting
CVE-2023-6487
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C