{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-67478 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-67478 is a vulnerability in Wikimedia Foundation CheckUser, published on 3 Feb 2026. 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-2025-67478 and fix it if it is affected.\n\nWhat it is: CVE-2025-67478 is a vulnerability in Wikimedia Foundation CheckUser, published on 3 Feb 2026. 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-2025-67478 in the wild and no public exploit code.\n\nAffected product: Wikimedia Foundation CheckUser. 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-2025-67478/ (Markdown: https://insights.sbomify.com/CVE-2025-67478/index.md)","id":"CVE-2025-67478","markdown":"https://insights.sbomify.com/CVE-2025-67478/index.md","name":"CVE-2025-67478","record":{"aliases":["DEBIAN-CVE-2025-67478","GHSA-rg4c-x95m-9m4f","UBUNTU-CVE-2025-67478"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MediaWiki CheckUser extension","requires_auth":"none","summary":"Attackers can exploit email composition flaws to potentially expose sensitive user data when usernames contain special characters.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"wikimedia-foundation","cpe":[{"product":"checkuser","vendor":"mediawiki"}],"cvss":{"score":0,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[],"description":"Vulnerability in Wikimedia Foundation CheckUser. This vulnerability is associated with program files includes/Mail/UserMailer.Php.\n\nThis issue affects CheckUser: from * before 1.39.14, 1.43.4, 1.44.1.","ecosystems":[],"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":"Wrong E-Mail address composition for usernames with a comma and Umlauts in it like \"Döe, Jähn\"","id":"CVE-2025-67478","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Magic word replacement in legacy parser allows using reserved data attributes through wikitext","id":"CVE-2025-67479"},"packages":[],"prev":{"headline":"Stored XSS through a system message in Special:ApiSandbox","id":"CVE-2025-67477"},"products":["CheckUser"],"published":"2026-02-03","related":[{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-2940","kev_date_added":null,"published":"2015-04-13"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2019-18611","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2019-16529","kev_date_added":null,"published":"2020-03-19"},{"cvss_score":4.8,"headline":"Suggested investigations: Handle suppressed usernames","id":"CVE-2026-34090","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":1.3,"headline":"Special:GlobalContributions shows edits on wikis the viewer doesn't have access to","id":"CVE-2025-61658","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":0,"headline":"Stored XSS through system messages in CheckUser","id":"CVE-2025-61648","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":0,"headline":"i18n XSS through Special:CheckUser CheckUser helper","id":"CVE-2025-61651","kev_date_added":null,"published":"2026-02-03"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["Wikimedia Foundation"]},"summary":"Attackers can exploit email composition flaws to potentially expose sensitive user data when usernames contain special characters.","url":"https://insights.sbomify.com/CVE-2025-67478/"}