{"answers":{"affected":"2 open source packages ship an affected version, including flarum/framework. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19133 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19133 is a medium-severity vulnerability in n/a, published on 9 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19133 and fix it if it is affected.\n\nWhat it is: CVE-2018-19133 is a medium-severity vulnerability in n/a, published on 9 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-19133 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- flarum/framework (Packagist): affected all versions up to 0.1.0-beta.7.1; no fix listed\n- flarum/framework (Packagist): affected all versions up to 0.1.0-beta.7.1; no fix listed\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-2018-19133/ (Markdown: https://insights.sbomify.com/CVE-2018-19133/index.md)","id":"CVE-2018-19133","markdown":"https://insights.sbomify.com/CVE-2018-19133/index.md","name":"CVE-2018-19133","record":{"aliases":["GHSA-p6m5-x83r-hqmr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Flarum forum software","requires_auth":"none","summary":"An attacker can retrieve all user email addresses from the Flarum forum software due to a serious information leak.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flarum","vendor":"flarum"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Flarum Core 0.1.0-beta.7.1, a serious leak can get everyone's email address.","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":false,"headline":"Flarum Core Leaks PII","id":"CVE-2018-19133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-19134"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["0.1.0-beta.7.1"],"package":"flarum/framework","purl":null,"source":"GHSA-p6m5-x83r-hqmr"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["0.1.0-beta.7.1"],"package":"flarum/framework","purl":"pkg:composer/flarum/framework","source":"GHSA-p6m5-x83r-hqmr"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-19132"},"products":["n/a"],"published":"2018-11-09","related":[{"cvss_score":10,"headline":"XSS vulnerability with translator","id":"CVE-2021-32671","kev_date_added":null,"published":"2021-06-07"},{"cvss_score":9,"headline":"Cross site scripting vulnerability with discussion titles in flarum","id":"CVE-2022-41938","kev_date_added":null,"published":"2022-11-19"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-13183","kev_date_added":null,"published":"2019-07-07"},{"cvss_score":7.7,"headline":"Post mentions can be used to read any post on the forum without access control","id":"CVE-2023-22487","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":7.5,"headline":"Flarum mishandles invalidation of user email tokens","id":"CVE-2019-11514","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":7.1,"headline":"Server-Side Request Forgery via Avatar upload in flarum","id":"CVE-2023-40033","kev_date_added":null,"published":"2023-08-16"},{"cvss_score":6.8,"headline":"Flarum Vulnerable to Session Hijacking via Authoritative Subdomain Cookie Overwrite","id":"CVE-2025-27794","kev_date_added":null,"published":"2025-03-12"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"An attacker can retrieve all user email addresses from the Flarum forum software due to a serious information leak.","url":"https://insights.sbomify.com/CVE-2018-19133/"}