{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-0327 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-0327 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0327 is a medium-severity vulnerability in Typo3 Typo3, published on 21 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-0327 and fix it if it is affected.\n\nWhat it is: CVE-2006-0327 is a medium-severity vulnerability in Typo3 Typo3, published on 21 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-0327 in the wild and no public exploit code.\n\nAffected product: Typo3 Typo3. 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-2006-0327/ (Markdown: https://insights.sbomify.com/CVE-2006-0327/index.md)","id":"CVE-2006-0327","markdown":"https://insights.sbomify.com/CVE-2006-0327/index.md","name":"CVE-2006-0327","record":{"aliases":["GHSA-pc69-wrpv-h7r8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"none","summary":"Remote attackers can obtain sensitive path information via direct requests to specific PHP scripts due to improper error handling.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"TYPO3 3.7.1 allows remote attackers to obtain sensitive information via a direct request to (1) thumbs.php, (2) showpic.php, or (3) tables.php, which causes them to incorrectly define a variable and reveal the path in an error message when a require function call fails.","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":"Information disclosure in n/a","id":"CVE-2006-0327","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"typo3:typo3","products":["typo3:typo3"],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":11,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-0328"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2006-0325"},"products":["n/a"],"published":"2006-01-21","related":[{"cvss_score":10,"headline":"Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection","id":"CVE-2009-0258","kev_date_added":null,"published":"2009-01-22"},{"cvss_score":9.8,"headline":"Typo3 SQL injection due to faulty prepared statements","id":"CVE-2011-3583","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":9.8,"headline":"Typo3 Authentication Bypass","id":"CVE-2011-4628","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":8.8,"headline":"Persisted Cross-Site Scripting in Frontend Rendering in typo3","id":"CVE-2023-24814","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":8.8,"headline":"Cross-Site-Request-Forgery in Backend URI Handling in Typo3","id":"CVE-2021-41113","kev_date_added":null,"published":"2021-10-05"},{"cvss_score":8.8,"headline":"Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS","id":"CVE-2020-15098","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in TYPO3 CMS","id":"CVE-2020-11067","kev_date_added":null,"published":"2020-05-13"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive path information via direct requests to specific PHP scripts due to improper error handling.","url":"https://insights.sbomify.com/CVE-2006-0327/"}