{"answers":{"affected":"","exploited":"There is no known exploitation of DRUPAL-CONTRIB-2018-021 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"DRUPAL-CONTRIB-2018-021 is a vulnerability in drupal/jsonapi, published on 25 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for DRUPAL-CONTRIB-2018-021 and fix it if it is affected.\n\nWhat it is: DRUPAL-CONTRIB-2018-021 is a vulnerability in drupal/jsonapi, published on 25 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of DRUPAL-CONTRIB-2018-021 in the wild and no public exploit code.\n\nAffected product: drupal/jsonapi. 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/DRUPAL-CONTRIB-2018-021/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2018-021/index.md)","id":"DRUPAL-CONTRIB-2018-021","markdown":"https://insights.sbomify.com/DRUPAL-CONTRIB-2018-021/index.md","name":"DRUPAL-CONTRIB-2018-021","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Drupal JSON API module","requires_auth":"low_privilege","summary":"Attackers can perform unauthorized actions on behalf of authenticated users via CSRF if specific CORS settings are enabled.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This module provides a JSON API standards-compliant API for accessing and manipulating Drupal content and configuration entities.\n\nThe module doesn't provide CSRF protection when processing authenticated traffic using cookie-based authentication.\n\nThis vulnerability is mitigated by the fact that an attacker must be allowed to create or modify entities of a certain type, and a very specific and uncommon CORS configuration that allows all other pre-checks to be skipped.","ecosystems":["Packagist:https://packages.drupal.org/8"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"This module provides a JSON API standards-compliant API for accessing and manipulating Drupal content and configuration entities.","id":"DRUPAL-CONTRIB-2018-021","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Packagist:https://packages.drupal.org/8","fixed":["1.16.0"],"introduced":["0"],"last_affected":[],"package":"drupal/jsonapi","purl":"pkg:composer/drupal/jsonapi?repository_url=https:%2F%2Fpackages.drupal.org%2F8","source":"DRUPAL-CONTRIB-2018-021"}],"products":null,"published":"2018-04-25","related":[],"sources":[{"class":"attribution","licence":"MIT","name":"Drupal","prefix":"DRUPAL"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can perform unauthorized actions on behalf of authenticated users via CSRF if specific CORS settings are enabled.","url":"https://insights.sbomify.com/DRUPAL-CONTRIB-2018-021/"}