{"answers":{"affected":"2 open source packages ship an affected version, including mautic/core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-47059 in the wild and no public exploit code.","fix":"Upgrade mautic/core to 5.1.1 or later.","what":"CVE-2024-47059 is a medium-severity vulnerability in Mautic, published on 18 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47059 and fix it if it is affected.\n\nWhat it is: CVE-2024-47059 is a medium-severity vulnerability in Mautic, published on 18 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-47059 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mautic/core (Packagist): affected from 5.1.0; fixed in 5.1.1\n- mautic/core (Packagist): affected from 5.1.0; fixed in 5.1.1\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-2024-47059/ (Markdown: https://insights.sbomify.com/CVE-2024-47059/index.md)","id":"CVE-2024-47059","markdown":"https://insights.sbomify.com/CVE-2024-47059/index.md","name":"CVE-2024-47059","record":{"aliases":["GHSA-8vff-35qm-qjvv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mautic marketing automation","requires_auth":"low_privilege","summary":"Attackers can enumerate valid usernames by observing distinct error messages for weak passwords versus invalid credentials in Mautic.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Mautic","cpe":[{"product":"mautic","vendor":"acquia"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"When logging in with the correct username and incorrect weak password, the user receives the notification, that their password is too weak.\n\nHowever when an incorrect username is provided alongside with a weak password, the application responds with ’Invalid credentials’ notification.\n\nThis difference could be used to perform username enumeration.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Users enumeration - weak password login","id":"CVE-2024-47059","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"Unauthorized Access After Organization or Project Deactivation in Zitadel","id":"CVE-2024-47060"},"packages":[{"ecosystem":"Packagist","fixed":["5.1.1"],"introduced":["5.1.0"],"last_affected":[],"package":"mautic/core","purl":null,"source":"GHSA-8vff-35qm-qjvv"},{"ecosystem":"Packagist","fixed":["5.1.1"],"introduced":["5.1.0"],"last_affected":[],"package":"mautic/core","purl":"pkg:composer/mautic/core","source":"GHSA-8vff-35qm-qjvv"}],"prev":{"headline":"Cross-site Scripting (XSS) - stored (edit form HTML field)","id":"CVE-2024-47058"},"products":["Mautic"],"published":"2024-09-18","related":[{"cvss_score":9.6,"headline":"Cross-site Scripting vulnerability in Mautic's tracking pixel functionality","id":"CVE-2022-25772","kev_date_added":null,"published":"2022-06-20"},{"cvss_score":9.6,"headline":"Mautic is vulnerable to XSS vulnerability","id":"CVE-2020-35125","kev_date_added":null,"published":"2021-02-09"},{"cvss_score":9.6,"headline":"XSS vulnerability leveraged through referrers could allow un-authorized admin access in Mautic","id":"CVE-2020-35124","kev_date_added":null,"published":"2021-01-28"},{"cvss_score":9.1,"headline":"Remote Code Execution \u0026 File Deletion in Asset Uploads","id":"CVE-2024-47051","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9,"headline":"Mautic stored Cross-site Scripting (XSS)","id":"CVE-2020-35128","kev_date_added":null,"published":"2021-01-19"},{"cvss_score":8.8,"headline":"Mautic Cross-Site Request Forgery (CSRF)","id":"CVE-2017-8874","kev_date_added":null,"published":"2017-05-10"},{"cvss_score":8.3,"headline":"Sensitive Data Exposure due to inadequate user permission settings","id":"CVE-2022-25776","kev_date_added":null,"published":"2024-09-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2024-09-25","vendors":["Mautic"]},"summary":"Attackers can enumerate valid usernames by observing distinct error messages for weak passwords versus invalid credentials in Mautic.","url":"https://insights.sbomify.com/CVE-2024-47059/"}