{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-47812 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-47812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47812 is a medium-severity cross-site scripting vulnerability in miraheze ImportDump, published on 9 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47812 and fix it if it is affected.\n\nWhat it is: CVE-2024-47812 is a medium-severity cross-site scripting vulnerability in miraheze ImportDump, published on 9 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-47812 in the wild and no public exploit code.\n\nAffected product: miraheze ImportDump. 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-2024-47812/ (Markdown: https://insights.sbomify.com/CVE-2024-47812/index.md)","id":"CVE-2024-47812","markdown":"https://insights.sbomify.com/CVE-2024-47812/index.md","name":"CVE-2024-47812","record":{"aliases":["GHSA-465h-45v4-6fx9"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"MediaWiki extension","requires_auth":"high_privilege","summary":"Administrators can inject XSS payloads into date messages, allowing attackers to execute scripts against users viewing the import queue.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"ImportDump is an extension for mediawiki designed to automate user import requests. Anyone who can edit the interface strings of a wiki (typically administrators and interface admins) can embed XSS payloads in the messages for dates, and thus XSS anyone who views Special:RequestImportQueue. This issue has been patched in commit `d054b95` and all users are advised to apply this commit to their branch. Users unable to upgrade may either Prevent access to Special:RequestImportQueue on all wikis, except for the global wiki; and If an interface administrator (or equivalent) level protection is available (which is not provided by default) on the global wiki, protect the affected messages up to that level. This causes the XSS to be virtually useless as users with those rights can already edit Javascript pages. Or Prevent access to Special:RequestImportQueue altogether.","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":"Cross-site Scripting (XSS) on Special:RequestImportQueue when displaying request date in ImportDump","id":"CVE-2024-47812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Wasmtime race condition could lead to WebAssembly control-flow integrity and type safety violations","id":"CVE-2024-47813"},"packages":[],"prev":{"headline":"Use after free in Foxit Reader","id":"CVE-2024-47810"},"products":["ImportDump"],"published":"2024-10-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-10-09","vendors":["miraheze"]},"summary":"Administrators can inject XSS payloads into date messages, allowing attackers to execute scripts against users viewing the import queue.","url":"https://insights.sbomify.com/CVE-2024-47812/"}