{"answers":{"affected":"","exploited":"There is no known exploitation of DRUPAL-CONTRIB-2019-093 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"DRUPAL-CONTRIB-2019-093 is a missing authorization vulnerability in drupal/taxonomy_access_fix, published on 11 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for DRUPAL-CONTRIB-2019-093 and fix it if it is affected.\n\nWhat it is: DRUPAL-CONTRIB-2019-093 is a missing authorization vulnerability in drupal/taxonomy_access_fix, published on 11 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of DRUPAL-CONTRIB-2019-093 in the wild and no public exploit code.\n\nAffected product: drupal/taxonomy_access_fix. 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-2019-093/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-093/index.md)","id":"DRUPAL-CONTRIB-2019-093","markdown":"https://insights.sbomify.com/DRUPAL-CONTRIB-2019-093/index.md","name":"DRUPAL-CONTRIB-2019-093","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Drupal taxonomy module","requires_auth":"low_privilege","summary":"Authenticated users with basic content access can view unpublished taxonomy terms and access restricted administrative routes due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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 extends access handling of Drupal Core's Taxonomy module.\n\nThe module doesn't sufficiently check,\n\n* if a given entity should be access controlled, defaulting to allowing access even to unpublished Taxonomy Terms.\n* if certain administrative routes should be access controlled, defaulting to allowing access even to users without permission to access these administrative routes.\n\nThe vulnerability is mitigated by the facts, that\n\n* the user interface to change the status of Taxonomy Terms has been released in Drupal Core 8.8 and a custom or contributed module is required in earlier versions of Drupal Core to mark Taxonomy Terms as unpublished.\n* all entity operations (except the view operation) available on affected administrative routes still require appropriate permissions.\n* an attacker must have a role with permission to either access content or view a Taxonomy Term in a vocabulary.","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 extends access handling of Drupal Core's Taxonomy module.","id":"DRUPAL-CONTRIB-2019-093","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Packagist:https://packages.drupal.org/8","fixed":["2.7.0"],"introduced":["0"],"last_affected":[],"package":"drupal/taxonomy_access_fix","purl":"pkg:composer/drupal/taxonomy_access_fix?repository_url=https:%2F%2Fpackages.drupal.org%2F8","source":"DRUPAL-CONTRIB-2019-093"}],"products":null,"published":"2019-12-11","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":"Authenticated users with basic content access can view unpublished taxonomy terms and access restricted administrative routes due to missing authorization checks.","url":"https://insights.sbomify.com/DRUPAL-CONTRIB-2019-093/"}