{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-9839 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-9839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-9839 is a medium-severity missing authorization vulnerability in Mantisbt Mantisbt, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-9839 and fix it if it is affected.\n\nWhat it is: CVE-2018-9839 is a medium-severity missing authorization vulnerability in Mantisbt Mantisbt, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-9839 in the wild and no public exploit code.\n\nAffected product: Mantisbt Mantisbt. 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-2018-9839/ (Markdown: https://insights.sbomify.com/CVE-2018-9839/index.md)","id":"CVE-2018-9839","markdown":"https://insights.sbomify.com/CVE-2018-9839/index.md","name":"CVE-2018-9839","record":{"aliases":["GHSA-w7gq-xmg2-xcrj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MantisBT bug tracker","requires_auth":"low_privilege","summary":"Authenticated users can view and expose private issue details by manipulating parameters during the clone operation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mantisbt","vendor":"mantisbt"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in MantisBT through 1.3.14, and 2.0.0. Using a crafted request on bug_report_page.php (modifying the 'm_id' parameter), any user with REPORTER access or above is able to view any private issue's details (summary, description, steps to reproduce, additional information) when cloning it. By checking the 'Copy issue notes' and 'Copy attachments' checkboxes and completing the clone operation, this data also becomes public (except private notes).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing authorization in n/a","id":"CVE-2018-9839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mantisbt:mantisbt","products":["mantisbt:mantisbt"],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2018-9840"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2018-9838"},"products":["n/a"],"published":"2019-06-06","related":[{"cvss_score":9.6,"headline":"MantisBT allows cross-site scripting (XSS) via crafted filename","id":"CVE-2019-15074","kev_date_added":null,"published":"2019-08-21"},{"cvss_score":9.3,"headline":"MantisBT SOAP API has an authentication bypass vulnerability on MySQL","id":"CVE-2026-30849","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.8,"headline":"MantisBT: Authentication bypass for some passwords due to PHP type juggling","id":"CVE-2025-47776","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":8.8,"headline":"MantisBT allows arbitrary password reset","id":"CVE-2017-7615","kev_date_added":null,"published":"2017-04-16"},{"cvss_score":8.6,"headline":"MantisBT Vulnerable to Stored HTML Injection in Tag Delete Confirmation","id":"CVE-2026-33517","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.6,"headline":"MantisBT has Stored HTML Injection / XSS when displaying Tags in Timeline","id":"CVE-2026-33548","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.3,"headline":"MantisBT Host Header Injection vulnerability","id":"CVE-2024-23830","kev_date_added":null,"published":"2024-02-20"}],"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-05","vendors":["n/a"]},"summary":"Authenticated users can view and expose private issue details by manipulating parameters during the clone operation.","url":"https://insights.sbomify.com/CVE-2018-9839/"}