{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4526 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4526 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4526 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 15 Sep 2020. 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-2020-4526 and fix it if it is affected.\n\nWhat it is: CVE-2020-4526 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 15 Sep 2020. 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-2020-4526 in the wild and no public exploit code.\n\nAffected product: Ibm Maximo Asset Management. 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-2020-4526/ (Markdown: https://insights.sbomify.com/CVE-2020-4526/index.md)","id":"CVE-2020-4526","markdown":"https://insights.sbomify.com/CVE-2020-4526/index.md","name":"CVE-2020-4526","record":{"aliases":["GHSA-rf2c-rjfm-w7w2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Asset Management","requires_auth":"none","summary":"Attackers can trick authenticated users into performing unauthorized actions in IBM Maximo Asset Management via cross-site request forgery.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_asset_management","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AC:L/A:N/AV:N/I:L/S:U/C:N/UI:R/PR:N/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"IBM Maximo Asset Management 7.6.0 and 7.6.1 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 182436.","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":"Cross-site request forgery in Maximo Asset Management","id":"CVE-2020-4526","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management"],"type":"csrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Planning Analytics","id":"CVE-2020-4527"},"packages":[],"prev":{"headline":"Cross-site scripting in Rational Rhapsody Design Manager","id":"CVE-2020-4525"},"products":["Maximo Asset Management"],"published":"2020-09-15","related":[{"cvss_score":9.8,"headline":"Auth bypass in Maximo Asset Management","id":"CVE-2020-4493","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":9.8,"headline":"SQL injection in Maximo Asset Management","id":"CVE-2017-1175","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":8.8,"headline":"Deserialization in Maximo Asset Management","id":"CVE-2020-4521","kev_date_added":null,"published":"2020-09-15"},{"cvss_score":8.8,"headline":"Hardcoded credentials in Maximo Asset Management","id":"CVE-2018-1524","kev_date_added":null,"published":"2018-08-03"},{"cvss_score":8.8,"headline":"SQL injection in Maximo Asset Management","id":"CVE-2018-1414","kev_date_added":null,"published":"2018-02-22"},{"cvss_score":8.8,"headline":"File upload in Maximo Asset Management","id":"CVE-2017-1499","kev_date_added":null,"published":"2018-02-14"},{"cvss_score":8.8,"headline":"Command injection in Maximo Asset Management","id":"CVE-2016-9984","kev_date_added":null,"published":"2017-06-13"}],"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-09-16","vendors":["IBM"]},"summary":"Attackers can trick authenticated users into performing unauthorized actions in IBM Maximo Asset Management via cross-site request forgery.","url":"https://insights.sbomify.com/CVE-2020-4526/"}