{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53906 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53906 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53906 is a medium-severity path traversal vulnerability in MyComplianceOffice MCO, published on 1 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53906 and fix it if it is affected.\n\nWhat it is: CVE-2026-53906 is a medium-severity path traversal vulnerability in MyComplianceOffice MCO, published on 1 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53906 in the wild and no public exploit code.\n\nAffected product: MyComplianceOffice MCO. 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-2026-53906/ (Markdown: https://insights.sbomify.com/CVE-2026-53906/index.md)","id":"CVE-2026-53906","markdown":"https://insights.sbomify.com/CVE-2026-53906/index.md","name":"CVE-2026-53906","record":{"aliases":["GHSA-qwcf-5293-mm28"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MCO compliance software","requires_auth":"high_privilege","summary":"Attackers can write files to arbitrary locations and disclose server paths via improper filename validation in MCO's export and upload features.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"mycomplianceoffice","vendor":"mycomplianceoffice"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"MCO is vulnerable to Path Disclosure and Path Traversal in file handling functionality related to data export and upload. Improper validation of the filename parameter allows writing files to arbitrary locations as well as indirect disclosure of absolute server paths through error messages.\n\nBecause vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.","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":"Path Disclosure and Path Traversal in MCO","id":"CVE-2026-53906","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Stored Cross‑Site Scripting in MCO","id":"CVE-2026-53907"},"packages":[],"prev":{"headline":"Unauthorized Access to Administrator ACL View in MCO","id":"CVE-2026-53905"},"products":["MCO"],"published":"2026-07-01","related":[{"cvss_score":7.1,"headline":"Privilege Escalation in MCO","id":"CVE-2026-53902","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":6.9,"headline":"User Enumeration in MCO","id":"CVE-2026-53908","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":5.3,"headline":"Insecure Direct Object Reference in MCO","id":"CVE-2026-53903","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":5.3,"headline":"Unauthorized Access to Administrator ACL View in MCO","id":"CVE-2026-53905","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":5.3,"headline":"Arbitrary File Upload in MCO","id":"CVE-2026-53909","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":4.8,"headline":"Stored Cross‑Site Scripting in MCO","id":"CVE-2026-53907","kev_date_added":null,"published":"2026-07-01"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["MyComplianceOffice"]},"summary":"Attackers can write files to arbitrary locations and disclose server paths via improper filename validation in MCO's export and upload features.","url":"https://insights.sbomify.com/CVE-2026-53906/"}