{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24767 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24767 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24767 is a medium-severity vulnerability in Unknown Redirect 404 Error Page to Homepage or Custom Page with Logs, published on 8 Nov 2021. 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-2021-24767 and fix it if it is affected.\n\nWhat it is: CVE-2021-24767 is a medium-severity vulnerability in Unknown Redirect 404 Error Page to Homepage or Custom Page with Logs, published on 8 Nov 2021. 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-2021-24767 in the wild and no public exploit code.\n\nAffected product: Unknown Redirect 404 Error Page to Homepage or Custom Page with Logs. 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-2021-24767/ (Markdown: https://insights.sbomify.com/CVE-2021-24767/index.md)","id":"CVE-2021-24767","markdown":"https://insights.sbomify.com/CVE-2021-24767/index.md","name":"CVE-2021-24767","record":{"aliases":["GHSA-q43p-2mh4-5jv2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"A CSRF vulnerability in a WordPress plugin allows attackers to force logged-in admins to delete logs, compromising audit trails.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"redirect_404_error_page_to_homepage_or_custom_page_with_logs","vendor":"wpvibes"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Redirect 404 Error Page to Homepage or Custom Page with Logs WordPress plugin before 1.7.9 does not check for CSRF when deleting logs, which could allow attacker to make a logged in admin delete them via a CSRF attack","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":"Redirect 404 Error Page to Homepage or Custom Page with Logs \u003c 1.7.9 - Log Deletion via CSRF","id":"CVE-2021-24767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"WP RSS Aggregator \u003c 4.19.2 - Admin+ Stored Cross-Site Scripting","id":"CVE-2021-24768"},"packages":[],"prev":{"headline":"404 to 301 \u003c 3.0.9 - Logs Deletion via CSRF","id":"CVE-2021-24766"},"products":["Redirect 404 Error Page to Homepage or Custom Page with Logs"],"published":"2021-11-08","related":[{"cvss_score":7.6,"headline":"WordPress Redirect 404 Error Page to Homepage or Custom Page with Logs Plugin \u003c= 1.8.7 is vulnerable to SQL Injection","id":"CVE-2023-47530","kev_date_added":null,"published":"2023-12-18"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"A CSRF vulnerability in a WordPress plugin allows attackers to force logged-in admins to delete logs, compromising audit trails.","url":"https://insights.sbomify.com/CVE-2021-24767/"}