{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3407 exists.","fix":"No fix has been published for CVE-2024-3407 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3407 is a medium-severity vulnerability in Unknown WP Prayer, published on 15 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3407 and fix it if it is affected.\n\nWhat it is: CVE-2024-3407 is a medium-severity vulnerability in Unknown WP Prayer, published on 15 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3407 exists.\n\nAffected product: Unknown WP Prayer. 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-3407/ (Markdown: https://insights.sbomify.com/CVE-2024-3407/index.md)","id":"CVE-2024-3407","markdown":"https://insights.sbomify.com/CVE-2024-3407/index.md","name":"CVE-2024-3407","record":{"aliases":["GHSA-53j6-rqp4-4h6m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can trick logged-in users into deleting arbitrary prayers via CSRF in the WP Prayer WordPress plugin.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_prayer","vendor":"goprayer"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Prayer WordPress plugin through 2.0.9 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WP Prayer \u003c= 2.0.9 - Arbitrary Prayer Deletion via CSRF","id":"CVE-2024-3407","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Authentication Bypass and RCE in man-group/dtale","id":"CVE-2024-3408"},"packages":[],"prev":{"headline":"WP Prayer \u003c= 2.0.9 - Email Settings Update via CSRF","id":"CVE-2024-3406"},"products":["WP Prayer"],"published":"2024-05-15","related":[{"cvss_score":8.8,"headline":"WP Prayer \u003c= 2.0.9 - Email Settings Update via CSRF","id":"CVE-2024-3406","kev_date_added":null,"published":"2024-05-15"},{"cvss_score":7.6,"headline":"WP Prayer \u003c= 2.0.9 - Settings Update via CSRF","id":"CVE-2024-3405","kev_date_added":null,"published":"2024-05-15"},{"cvss_score":5.9,"headline":"WordPress WP Prayer Plugin \u003c= 1.9.6 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-25705","kev_date_added":null,"published":"2023-04-07"},{"cvss_score":5.4,"headline":"WP Prayer \u003c 1.6.2 - Authenticated Stored Cross-Site Scripting (XSS)","id":"CVE-2021-24313","kev_date_added":null,"published":"2021-06-01"},{"cvss_score":4.3,"headline":"WP Prayer \u003c= 1.6.5 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4412","kev_date_added":null,"published":"2023-07-12"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Unknown"]},"summary":"Attackers can trick logged-in users into deleting arbitrary prayers via CSRF in the WP Prayer WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-3407/"}