{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-26180 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-26180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-26180 is a high-severity vulnerability in n/a, published on 8 Apr 2022. 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-2022-26180 and fix it if it is affected.\n\nWhat it is: CVE-2022-26180 is a high-severity vulnerability in n/a, published on 8 Apr 2022. 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-2022-26180 in the wild and no public exploit code.\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-2022-26180/ (Markdown: https://insights.sbomify.com/CVE-2022-26180/index.md)","id":"CVE-2022-26180","markdown":"https://insights.sbomify.com/CVE-2022-26180/index.md","name":"CVE-2022-26180","record":{"aliases":["GHSA-9v79-hrc5-gvgm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"qdPM project management","requires_auth":"none","summary":"Attackers can trick authenticated users into modifying their account settings via a Cross-Site Request Forgery vulnerability in qdPM.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"qdpm","vendor":"qdpm"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","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":"qdPM 9.2 allows Cross-Site Request Forgery (CSRF) via the index.php/myAccount/update URI.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2022-04-07","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-04-07","kind":"exploitdb","ref":"50854","stars":null,"title":"qdPM 9.2 - Cross-site Request Forgery (CSRF)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-26180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-26181"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2022-26174"},"products":["n/a"],"published":"2022-04-08","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-45856","kev_date_added":null,"published":"2023-10-14"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-11811","kev_date_added":null,"published":"2020-04-16"},{"cvss_score":8.8,"headline":"qdPM 9.1 SQL Injection via search_by_extrafields Parameter","id":"CVE-2019-25669","kev_date_added":null,"published":"2026-04-05"},{"cvss_score":8.8,"headline":"qdPM 9.1 SQL Injection via filter_by Parameters","id":"CVE-2018-25208","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2020-26165","kev_date_added":null,"published":"2020-12-31"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-7246","kev_date_added":null,"published":"2020-01-21"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can trick authenticated users into modifying their account settings via a Cross-Site Request Forgery vulnerability in qdPM.","url":"https://insights.sbomify.com/CVE-2022-26180/"}