{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42607 exists.","fix":"No fix has been published for CVE-2024-42607 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-42607 is a high-severity vulnerability in n/a, published on 20 Aug 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-42607 and fix it if it is affected.\n\nWhat it is: CVE-2024-42607 is a high-severity vulnerability in n/a, published on 20 Aug 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42607 exists.\n\nAffected product: n/a. 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-42607/ (Markdown: https://insights.sbomify.com/CVE-2024-42607/index.md)","id":"CVE-2024-42607","markdown":"https://insights.sbomify.com/CVE-2024-42607/index.md","name":"CVE-2024-42607","record":{"aliases":["GHSA-xch8-494w-5px5"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Pligg CMS","requires_auth":"none","summary":"An attacker can trick an authenticated admin into triggering a database backup via CSRF in Pligg CMS, potentially exposing sensitive data or disrupting operations.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pligg_cms","vendor":"pligg"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_backup.php?dobackup=database","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-42607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2024-42608"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2024-42606"},"products":["n/a"],"published":"2024-08-20","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-37677","kev_date_added":null,"published":"2023-07-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-34955","kev_date_added":null,"published":"2022-08-02"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-34956","kev_date_added":null,"published":"2022-08-02"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-42604","kev_date_added":null,"published":"2024-08-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-42608","kev_date_added":null,"published":"2024-08-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-42610","kev_date_added":null,"published":"2024-08-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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-20","vendors":["n/a"]},"summary":"An attacker can trick an authenticated admin into triggering a database backup via CSRF in Pligg CMS, potentially exposing sensitive data or disrupting operations.","url":"https://insights.sbomify.com/CVE-2024-42607/"}