{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-3938 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-3938 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-3938 is a medium-severity vulnerability in n/a, published on 31 Jul 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-3938 and fix it if it is affected.\n\nWhat it is: CVE-2006-3938 is a medium-severity vulnerability in n/a, published on 31 Jul 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-3938 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-2006-3938/ (Markdown: https://insights.sbomify.com/CVE-2006-3938/index.md)","id":"CVE-2006-3938","markdown":"https://insights.sbomify.com/CVE-2006-3938/index.md","name":"CVE-2006-3938","record":{"aliases":["GHSA-68x3-76p3-3cjc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"DotClear blog software","requires_auth":"none","summary":"Remote attackers can obtain sensitive installation path information by requesting specific PHP files that reveal paths in error messages.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dotclear","vendor":"dotclear"}],"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":"DotClear allows remote attackers to obtain sensitive information via a direct request for (1) edit_cat.php, (2) index.php, (3) edit_link.php in ecrire/tools/blogroll/; (4) syslog/index.php, (5) thememng/index.php, (6) toolsmng/index.php, (7) utf8convert/index.php in /ecrire/tools/; (8) /ecrire/inc/connexion.php and (9) /inc/session.php; (10) class.blog.php, (11) class.blogcomment.php, (12) and class.blogpost.php in /inc/classes/; (13) append.php, (14) class.xblog.php, (15) class.xblogcomment.php, and (16) class.xblogpost.php in /layout/; (17) form.php, (18) list.php, (19) post.php, or (20) template.php in /themes/default/, which reveal the installation path in error messages.","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-3938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":24,"next":{"headline":"Missing authorization in n/a","id":"CVE-2006-3939"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2006-3937"},"products":["n/a"],"published":"2006-07-31","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2005-3957","kev_date_added":null,"published":"2005-12-01"},{"cvss_score":9.3,"headline":"File upload in n/a","id":"CVE-2008-3232","kev_date_added":null,"published":"2008-07-18"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2015-8832","kev_date_added":null,"published":"2017-02-09"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2016-7902","kev_date_added":null,"published":"2017-01-04"},{"cvss_score":8.7,"headline":"Dotclear 2.25.3 Authenticated Remote Code Execution via File Upload","id":"CVE-2023-53952","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":8.7,"headline":"Dotclear 2.29 Remote Code Execution via Authenticated File Upload","id":"CVE-2024-58281","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.5,"headline":"Deserialization in n/a","id":"CVE-2014-1613","kev_date_added":null,"published":"2014-05-16"}],"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 installation path information by requesting specific PHP files that reveal paths in error messages.","url":"https://insights.sbomify.com/CVE-2006-3938/"}