{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17996 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17996 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17996 is a medium-severity vulnerability in n/a, published on 17 Mar 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-17996 and fix it if it is affected.\n\nWhat it is: CVE-2018-17996 is a medium-severity vulnerability in n/a, published on 17 Mar 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-17996 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-2018-17996/ (Markdown: https://insights.sbomify.com/CVE-2018-17996/index.md)","id":"CVE-2018-17996","markdown":"https://insights.sbomify.com/CVE-2018-17996/index.md","name":"CVE-2018-17996","record":{"aliases":["GHSA-gv2w-m3wh-vwhw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LayerBB forum","requires_auth":"none","summary":"Cross-site request forgery allows attackers to add or delete users and content in LayerBB forums.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"layerbb","vendor":"layerbb"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"LayerBB before 1.1.3 allows CSRF for adding a user via admin/new_user.php, deleting a user via admin/members.php/delete_user/, and deleting content via mod/delete.php/.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-02-14","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-02-14","kind":"exploitdb","ref":"46379","stars":null,"title":"LayerBB 1.1.2 - Cross-Site Request Forgery (Add Admin)"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-17996","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-17997"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-17990"},"products":["n/a"],"published":"2019-03-17","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2019-13973","kev_date_added":null,"published":"2019-07-19"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-17988","kev_date_added":null,"published":"2019-03-07"},{"cvss_score":8.8,"headline":"LayerBB before 1.1.4 has multiple CSRF issues, as demonstrated by changing the System Settings via admin/general.php.","id":"CVE-2019-16531","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-13974","kev_date_added":null,"published":"2019-07-19"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-13972","kev_date_added":null,"published":"2019-07-19"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-17997","kev_date_added":null,"published":"2019-03-17"}],"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-05","vendors":["n/a"]},"summary":"Cross-site request forgery allows attackers to add or delete users and content in LayerBB forums.","url":"https://insights.sbomify.com/CVE-2018-17996/"}