{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1858 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1858 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1858 is a medium-severity vulnerability in Ibm Api Connect, published on 25 Jun 2019. 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-2018-1858 and fix it if it is affected.\n\nWhat it is: CVE-2018-1858 is a medium-severity vulnerability in Ibm Api Connect, published on 25 Jun 2019. 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-2018-1858 in the wild and no public exploit code.\n\nAffected product: Ibm Api Connect. 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-2018-1858/ (Markdown: https://insights.sbomify.com/CVE-2018-1858/index.md)","id":"CVE-2018-1858","markdown":"https://insights.sbomify.com/CVE-2018-1858/index.md","name":"CVE-2018-1858","record":{"aliases":["GHSA-w7wc-46r3-xm6r"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM API Connect","requires_auth":"none","summary":"An attacker can trick users into performing unauthorized actions in IBM API Connect via cross-site request forgery.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"api_connect","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/C:L/AV:N/S:U/I:N/UI:R/AC:L/A:N/PR:N/RC:C/E:U/RL:O","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"IBM API Connect 5.0.0.0 through 5.0.8.6 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: 151256.","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 API Connect","id":"CVE-2018-1858","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:api_connect","products":["ibm:api_connect"],"type":"csrf","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in API Connect","id":"CVE-2018-1859"},"packages":[],"prev":{"headline":"Missing authorization in DB2 for Linux, UNIX and Windows","id":"CVE-2018-1857"},"products":["API Connect"],"published":"2019-06-25","related":[{"cvss_score":10,"headline":"Command injection in API Connect","id":"CVE-2019-4202","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":9.8,"headline":"Authentication bypass in IBM API Connect","id":"CVE-2025-13915","kev_date_added":null,"published":"2025-12-26"},{"cvss_score":9.8,"headline":"Command injection in API Connect","id":"CVE-2018-1469","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":9.1,"headline":"IBM API Connect SQL Injection","id":"CVE-2026-9074","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":9,"headline":"Information disclosure in API Connect","id":"CVE-2019-4008","kev_date_added":null,"published":"2019-02-07"},{"cvss_score":8.9,"headline":"Server-side request forgery in API Connect","id":"CVE-2019-4203","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":8.9,"headline":"Code injection in API Connect","id":"CVE-2018-1774","kev_date_added":null,"published":"2018-11-09"}],"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":"An attacker can trick users into performing unauthorized actions in IBM API Connect via cross-site request forgery.","url":"https://insights.sbomify.com/CVE-2018-1858/"}