{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12923 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12923 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12923 is a medium-severity vulnerability in Mailenable Mailenable, published on 8 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-12923 and fix it if it is affected.\n\nWhat it is: CVE-2019-12923 is a medium-severity vulnerability in Mailenable Mailenable, published on 8 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-12923 in the wild and no public exploit code.\n\nAffected product: Mailenable Mailenable. 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-12923/ (Markdown: https://insights.sbomify.com/CVE-2019-12923/index.md)","id":"CVE-2019-12923","markdown":"https://insights.sbomify.com/CVE-2019-12923/index.md","name":"CVE-2019-12923","record":{"aliases":["GHSA-2fvq-gwm3-84c2"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mail server software","requires_auth":"none","summary":"Attackers can bypass CSRF protection in MailEnable Enterprise Premium to force users to perform actions like sending emails or changing settings.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mailenable","vendor":"mailenable"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"In MailEnable Enterprise Premium 10.23, the potential cross-site request forgery (CSRF) protection mechanism was not implemented correctly and it was possible to bypass it by removing the anti-CSRF token parameter from the request. This could allow an attacker to manipulate a user into unwittingly performing actions within the application (such as sending email, adding contacts, or changing settings) on behalf of the attacker.","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":"Cross-site request forgery in n/a","id":"CVE-2019-12923","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mailenable:mailenable","products":["mailenable:mailenable"],"type":"csrf","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2019-12924"},"packages":[],"prev":{"headline":"phpMyAdmin Cross-Site Request Forgery (CSRF)","id":"CVE-2019-12922"},"products":["n/a"],"published":"2019-07-08","related":[{"cvss_score":10,"headline":"XML external entity in n/a","id":"CVE-2015-9280","kev_date_added":null,"published":"2019-01-16"},{"cvss_score":9.8,"headline":"Cross-site scripting in n/a","id":"CVE-2025-44148","kev_date_added":null,"published":"2025-06-03"},{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2019-12924","kev_date_added":null,"published":"2019-07-08"},{"cvss_score":9.8,"headline":"MailEnable before 8.60 allows Privilege Escalation because admin accounts could be created as a consequence of %0A mishandling in AUTH.TAB a","id":"CVE-2015-9278","kev_date_added":null,"published":"2019-01-16"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2015-9277","kev_date_added":null,"published":"2019-01-16"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2022-42136","kev_date_added":null,"published":"2023-01-13"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2019-12926","kev_date_added":null,"published":"2019-07-08"}],"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-04","vendors":["n/a"]},"summary":"Attackers can bypass CSRF protection in MailEnable Enterprise Premium to force users to perform actions like sending emails or changing settings.","url":"https://insights.sbomify.com/CVE-2019-12923/"}