{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-2299 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2299 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2299 is a medium-severity vulnerability in theluckywp LuckyWP Table of Contents, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-2299 and fix it if it is affected.\n\nWhat it is: CVE-2025-2299 is a medium-severity vulnerability in theluckywp LuckyWP Table of Contents, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-2299 in the wild and no public exploit code.\n\nAffected product: theluckywp LuckyWP Table of Contents. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-2299/ (Markdown: https://insights.sbomify.com/CVE-2025-2299/index.md)","id":"CVE-2025-2299","markdown":"https://insights.sbomify.com/CVE-2025-2299/index.md","name":"CVE-2025-2299","record":{"aliases":["GHSA-w67q-cmfr-rmhr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary scripts and potentially take over accounts by tricking administrators into clicking a link due to missing nonce validation.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"luckywp_table_of_contents","vendor":"theluckywp"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"LuckyWP Table of Contents \u003c= 2.1.10 - Cross-Site Request Forgery to Reflected Cross-Site Scripting","id":"CVE-2025-2299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Information exposure vulnerability in Hitachi Ops Center Common Services within Hitachi Ops Center OVA","id":"CVE-2025-2300"},"packages":[],"prev":{"headline":"Authenticated API Endpoint Allows Arbitrary File Deletion in Dremio Software","id":"CVE-2025-2298"},"products":["LuckyWP Table of Contents"],"published":"2025-04-03","related":[{"cvss_score":6.1,"headline":"LuckyWP Table of Contents \u003c= 2.1.5 - Reflected Cross-Site Scripting","id":"CVE-2024-2119","kev_date_added":null,"published":"2024-05-22"},{"cvss_score":5.5,"headline":"LuckyWP Table of Contents \u003c= 2.1.4 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-2953","kev_date_added":null,"published":"2024-05-22"},{"cvss_score":4.8,"headline":"LuckyWP Table of Contents \u003c 2.1.7 - Admin+ Stored XSS","id":"CVE-2024-9641","kev_date_added":null,"published":"2024-12-12"},{"cvss_score":4.6,"headline":"LuckyWP Table of Contents \u003c= 2.1.4 - Admin+ Stored XSS","id":"CVE-2024-2218","kev_date_added":null,"published":"2024-06-14"},{"cvss_score":4.4,"headline":"LuckyWP Table of Contents \u003c= 2.1.5 - Authenticated (Administrator+) Cross-Site Scripting","id":"CVE-2023-6487","kev_date_added":null,"published":"2024-05-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["theluckywp"]},"summary":"Unauthenticated attackers can execute arbitrary scripts and potentially take over accounts by tricking administrators into clicking a link due to missing nonce validation.","url":"https://insights.sbomify.com/CVE-2025-2299/"}