{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7213 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7213 is a medium-severity path traversal vulnerability in n/a, published on 24 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-7213 and fix it if it is affected.\n\nWhat it is: CVE-2019-7213 is a medium-severity path traversal vulnerability in n/a, published on 24 Apr 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-2019-7213 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-2019-7213/ (Markdown: https://insights.sbomify.com/CVE-2019-7213/index.md)","id":"CVE-2019-7213","markdown":"https://insights.sbomify.com/CVE-2019-7213/index.md","name":"CVE-2019-7213","record":{"aliases":["GHSA-vwrv-x97v-wggr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SmarterMail server","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit directory traversal to delete files or place malicious files, potentially leading to remote code execution on SmarterMail servers.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smartermail","vendor":"smartertools"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"SmarterTools SmarterMail 16.x before build 6985 allows directory traversal. An authenticated user could delete arbitrary files or could create files in new folders in arbitrary locations on the mail server. This could lead to command execution on the server for instance by putting files inside the web directories.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-09-11","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-09-11T21:01:53Z","kind":"github_poc","ref":"https://github.com/secunnix/CVE-2019-7213","stars":1,"title":" SmarterMail 16.x Exploit"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2019-7213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Deserialization in n/a","id":"CVE-2019-7214"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2019-7212"},"products":["n/a"],"published":"2019-04-24","related":[{"cvss_score":10,"headline":"SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type","id":"CVE-2025-52691","kev_date_added":"2026-01-26","published":"2025-12-29"},{"cvss_score":9.3,"headline":"SmarterTools SmarterMail Missing Authentication for Critical Function","id":"CVE-2026-24423","kev_date_added":"2026-02-05","published":"2026-01-23"},{"cvss_score":9.3,"headline":"SmarterTools SmarterMail Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2026-23760","kev_date_added":"2026-01-26","published":"2026-01-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-32234","kev_date_added":null,"published":"2021-11-17"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2019-7214","kev_date_added":null,"published":"2019-04-24"},{"cvss_score":8.7,"headline":"SmarterTools SmarterMail \u003c Build 9560 Server Local File Inclusion via the /api/v1/report/summary/{type} API","id":"CVE-2026-7807","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.2,"headline":"SmarterTools SmarterMail \u003c Build 9610 Cryptographic Weakness via Weak RNG","id":"CVE-2026-40514","kev_date_added":null,"published":"2026-04-27"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Authenticated attackers can exploit directory traversal to delete files or place malicious files, potentially leading to remote code execution on SmarterMail servers.","url":"https://insights.sbomify.com/CVE-2019-7213/"}