{"answers":{"affected":"2 open source packages ship an affected version, including statamic/cms.","exploited":"There is no known exploitation of CVE-2024-36119 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to 5.6.2 or later.","what":"CVE-2024-36119 is a low-severity vulnerability in statamic cms, published on 30 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-36119 and fix it if it is affected.\n\nWhat it is: CVE-2024-36119 is a low-severity vulnerability in statamic cms, published on 30 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-36119 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected from 5.3.0; fixed in 5.6.2\n- statamic/cms (Packagist): affected from 5.3.0; fixed in 5.6.2\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-36119/ (Markdown: https://insights.sbomify.com/CVE-2024-36119/index.md)","id":"CVE-2024-36119","markdown":"https://insights.sbomify.com/CVE-2024-36119/index.md","name":"CVE-2024-36119","record":{"aliases":["GHSA-qvpj-w7xj-r6w9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Statamic CMS","requires_auth":"high_privilege","summary":"Statamic CMS stores password confirmations in plain text in user files when using specific registration forms and file-based accounts, exposing credentials to developers.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":1.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Statamic is a, Laravel + Git powered CMS designed for building websites. In affected versions users registering via the `user:register_form` tag will have their password confirmation stored in plain text in their user file. This only affects sites matching **all** of the following conditions: 1. Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week), 2. Using the `user:register_form` tag. 3. Using file-based user accounts. (Does not affect users stored in a database.), 4. Has users that have registered during that time period. (Existing users are not affected.). Additionally passwords are only visible to users that have access to read user yaml files, typically developers of the application itself. This issue has been patched in version 5.6.2, however any users registered during that time period and using the affected version range will still have the the `password_confirmation` value in their yaml files. We recommend that affected users have their password reset. System administrators are advised to upgrade their deployments. There are no known workarounds for this vulnerability. Anyone who commits their files to a public git repo, may consider clearing the sensitive data from the git history as it is likely that passwords were uploaded.","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":"Password confirmation stored in plain text via registration form in statamic/cms","id":"CVE-2024-36119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":4,"next":{"headline":"javascript-deobfuscator crafted payload can lead to code execution","id":"CVE-2024-36120"},"packages":[{"ecosystem":"Packagist","fixed":["5.6.2"],"introduced":["5.3.0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-qvpj-w7xj-r6w9"},{"ecosystem":"Packagist","fixed":["5.6.2"],"introduced":["5.3.0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-qvpj-w7xj-r6w9"}],"prev":{"headline":"Unauthorized viewing of workspace test cases in MeterSphere","id":"CVE-2024-36118"},"products":["cms"],"published":"2024-05-30","related":[],"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":"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-08-02","vendors":["statamic"]},"summary":"Statamic CMS stores password confirmations in plain text in user files when using specific registration forms and file-based accounts, exposing credentials to developers.","url":"https://insights.sbomify.com/CVE-2024-36119/"}