{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-1501 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-1501 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1501 is a medium-severity vulnerability in webfactory Database Reset, published on 21 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-1501 and fix it if it is affected.\n\nWhat it is: CVE-2024-1501 is a medium-severity vulnerability in webfactory Database Reset, published on 21 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-1501 in the wild and no public exploit code.\n\nAffected product: webfactory Database Reset. 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-1501/ (Markdown: https://insights.sbomify.com/CVE-2024-1501/index.md)","id":"CVE-2024-1501","markdown":"https://insights.sbomify.com/CVE-2024-1501/index.md","name":"CVE-2024-1501","record":{"aliases":["GHSA-2j24-h5g8-5q33"],"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":"Unauthenticated attackers can trick administrators into installing the WP Reset plugin via CSRF, bypassing authorization controls.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_database_reset","vendor":"webfactoryltd"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Database Reset plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.22. This is due to missing or incorrect nonce validation on the install_wpr() function. This makes it possible for unauthenticated attackers to install the WP Reset Plugin 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":"Database Reset \u003c= 3.22 - Cross-Site Request Forgery to WP Reset Plugin Installation","id":"CVE-2024-1501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in Tutor LMS – eLearning and online course solution","id":"CVE-2024-1502"},"packages":[],"prev":{"headline":"Cross-site scripting in Royal Addons for Elementor – Addons and Templates Kit for Elementor","id":"CVE-2024-1500"},"products":["Database Reset"],"published":"2024-02-21","related":[{"cvss_score":9.9,"headline":"Privilege escalation in n/a","id":"CVE-2020-7047","kev_date_added":null,"published":"2020-01-16"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2020-7048","kev_date_added":null,"published":"2020-01-16"}],"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":["webfactory"]},"summary":"Unauthenticated attackers can trick administrators into installing the WP Reset plugin via CSRF, bypassing authorization controls.","url":"https://insights.sbomify.com/CVE-2024-1501/"}