{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-24875 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-24875 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-24875 is a medium-severity vulnerability in Yannick Lefebvre Link Library, published on 12 Feb 2024. 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-2024-24875 and fix it if it is affected.\n\nWhat it is: CVE-2024-24875 is a medium-severity vulnerability in Yannick Lefebvre Link Library, published on 12 Feb 2024. 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-2024-24875 in the wild and no public exploit code.\n\nAffected product: Yannick Lefebvre Link Library. 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-2024-24875/ (Markdown: https://insights.sbomify.com/CVE-2024-24875/index.md)","id":"CVE-2024-24875","markdown":"https://insights.sbomify.com/CVE-2024-24875/index.md","name":"CVE-2024-24875","record":{"aliases":["GHSA-xhcp-wrwf-p86r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick authenticated users into performing unwanted actions in the Link Library WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"link_library","vendor":"ylefebvre"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in Yannick Lefebvre Link Library.This issue affects Link Library: from n/a through 7.5.13.","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":"WordPress Link Library Plugin \u003c= 7.5.13 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2024-24875","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Admin Menu Editor Plugin \u003c= 1.12 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2024-24876"},"packages":[],"prev":{"headline":"WordPress Polls CP plugin \u003c= 1.0.71 - Content Injection vulnerability","id":"CVE-2024-24874"},"products":["Link Library"],"published":"2024-02-12","related":[{"cvss_score":7.5,"headline":"Link Library \u003c 7.2.8 - Unauthenticated Arbitrary Links Deletion","id":"CVE-2021-25093","kev_date_added":null,"published":"2022-02-01"},{"cvss_score":7.1,"headline":"WordPress Link Library plugin \u003c= 7.7.1 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-38711","kev_date_added":null,"published":"2024-07-20"},{"cvss_score":7.1,"headline":"WordPress Link Library plugin \u003c= 7.6.3 - Reflected Cross-Site Scripting (XSS) vulnerability","id":"CVE-2024-35687","kev_date_added":null,"published":"2024-06-08"},{"cvss_score":7.1,"headline":"WordPress Link Library plugin \u003c= 7.6 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29123","kev_date_added":null,"published":"2024-03-19"},{"cvss_score":7.1,"headline":"WordPress Link Library Plugin \u003c= 7.5.13 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2024-24879","kev_date_added":null,"published":"2024-02-08"},{"cvss_score":6.5,"headline":"WordPress Link Library plugin \u003c= 7.8 - Cross Site Scripting (XSS) Vulnerability","id":"CVE-2025-46237","kev_date_added":null,"published":"2025-04-22"},{"cvss_score":6.5,"headline":"Link Library \u003c= 7.6 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2024-1559","kev_date_added":null,"published":"2024-02-20"}],"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-28","vendors":["Yannick Lefebvre"]},"summary":"Attackers can trick authenticated users into performing unwanted actions in the Link Library WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-24875/"}