{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18611 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18611 is a medium-severity vulnerability in n/a, published on 29 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18611 and fix it if it is affected.\n\nWhat it is: CVE-2019-18611 is a medium-severity vulnerability in n/a, published on 29 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-18611 in the wild and no public exploit code.\n\nAffected product: n/a. 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-18611/ (Markdown: https://insights.sbomify.com/CVE-2019-18611/index.md)","id":"CVE-2019-18611","markdown":"https://insights.sbomify.com/CVE-2019-18611/index.md","name":"CVE-2019-18611","record":{"aliases":["GHSA-w3xh-g4rp-pcfc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MediaWiki extension","requires_auth":"low_privilege","summary":"Users with CheckUser access could view sensitive oversighted edit summaries via the API, exposing hidden data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"checkuser","vendor":"mediawiki"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in the CheckUser extension through 1.34 for MediaWiki. Certain sensitive information within oversighted edit summaries made available via the MediaWiki API was potentially visible to users with various levels of access to this extension. Said users should not have been able to view these oversighted edit summaries via the MediaWiki API.","ecosystems":[],"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":"Information disclosure in n/a","id":"CVE-2019-18611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-18612"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-18610"},"products":["n/a"],"published":"2019-10-29","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":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":"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-05","vendors":["n/a"]},"summary":"Users with CheckUser access could view sensitive oversighted edit summaries via the API, exposing hidden data.","url":"https://insights.sbomify.com/CVE-2019-18611/"}