{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-3881 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-3881 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-3881 is a high-severity vulnerability in n/a, published on 17 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-3881 and fix it if it is affected.\n\nWhat it is: CVE-2015-3881 is a high-severity vulnerability in n/a, published on 17 Mar 2017. 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-2015-3881 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-2015-3881/ (Markdown: https://insights.sbomify.com/CVE-2015-3881/index.md)","id":"CVE-2015-3881","markdown":"https://insights.sbomify.com/CVE-2015-3881/index.md","name":"CVE-2015-3881","record":{"aliases":["GHSA-g2c8-c2j8-3vp6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"qdPM project management","requires_auth":"none","summary":"Remote attackers can access sensitive configuration and log files in qdPM, potentially exposing credentials or internal details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"qdpm","vendor":"qdpm"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Information disclosure issue in qdPM 8.3 allows remote attackers to obtain sensitive information via a direct request to (1) core/config/databases.yml, (2) core/log/qdPM_prod.log, or (3) core/apps/qdPM/config/settings.yml.","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-2015-3881","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2015-3882"},"packages":[],"prev":{"headline":"phpBB Open Redirect","id":"CVE-2015-3880"},"products":["n/a"],"published":"2017-03-17","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-45856","kev_date_added":null,"published":"2023-10-14"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-11811","kev_date_added":null,"published":"2020-04-16"},{"cvss_score":8.8,"headline":"qdPM 9.1 SQL Injection via search_by_extrafields Parameter","id":"CVE-2019-25669","kev_date_added":null,"published":"2026-04-05"},{"cvss_score":8.8,"headline":"qdPM 9.1 SQL Injection via filter_by Parameters","id":"CVE-2018-25208","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-26180","kev_date_added":null,"published":"2022-04-08"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2020-26165","kev_date_added":null,"published":"2020-12-31"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-7246","kev_date_added":null,"published":"2020-01-21"}],"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-08-06","vendors":["n/a"]},"summary":"Remote attackers can access sensitive configuration and log files in qdPM, potentially exposing credentials or internal details.","url":"https://insights.sbomify.com/CVE-2015-3881/"}