{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-2075 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-2075 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-2075 is a high-severity missing authorization vulnerability in n/a, published on 16 Jun 2009. It can be exploited over the network."},"fix_prompt":"Check this codebase for CVE-2009-2075 and fix it if it is affected.\n\nWhat it is: CVE-2009-2075 is a high-severity missing authorization vulnerability in n/a, published on 16 Jun 2009. It can be exploited over the network.\nExploitation: There is no known exploitation of CVE-2009-2075 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-2009-2075/ (Markdown: https://insights.sbomify.com/CVE-2009-2075/index.md)","id":"CVE-2009-2075","markdown":"https://insights.sbomify.com/CVE-2009-2075/index.md","name":"CVE-2009-2075","record":{"aliases":["GHSA-6pj5-mm38-9526"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Drupal module","requires_auth":"unknown","summary":"The Nodequeue Drupal module fails to restrict access to node titles, potentially allowing unauthorized users to view sensitive information.","user_interaction":"unknown","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nodequeue","vendor":"angrydonuts"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Nodequeue 5.x before 5.x-2.7 and 6.x before 6.x-2.2, a module for Drupal, does not properly restrict access when displaying node titles, which has unknown impact and attack vectors.","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":"Missing authorization in n/a","id":"CVE-2009-2075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2009"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2009-2076"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2009-2074"},"products":["n/a"],"published":"2009-06-16","related":[],"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-17","vendors":["n/a"]},"summary":"The Nodequeue Drupal module fails to restrict access to node titles, potentially allowing unauthorized users to view sensitive information.","url":"https://insights.sbomify.com/CVE-2009-2075/"}