{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-32956 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-32956 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32956 is a high-severity SQL injection vulnerability in miraheze ManageWiki, published on 21 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-32956 and fix it if it is affected.\n\nWhat it is: CVE-2025-32956 is a high-severity SQL injection vulnerability in miraheze ManageWiki, published on 21 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-32956 in the wild and no public exploit code.\n\nAffected product: miraheze ManageWiki. 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-32956/ (Markdown: https://insights.sbomify.com/CVE-2025-32956/index.md)","id":"CVE-2025-32956","markdown":"https://insights.sbomify.com/CVE-2025-32956/index.md","name":"CVE-2025-32956","record":{"aliases":["GHSA-gg42-cv66-f5x7"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MediaWiki extension","requires_auth":"low_privilege","summary":"Attackers can inject SQL commands via namespace renaming in ManageWiki, potentially reading or modifying database content.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"managewiki","vendor":"miraheze"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"ManageWiki is a MediaWiki extension allowing users to manage wikis. Versions before commit f504ed8, are vulnerable to SQL injection when renaming a namespace in Special:ManageWiki/namespaces when using a page prefix (namespace name, which is the current namespace you are renaming) with an injection payload. This issue has been patched in commit f504ed8. A workaround for this vulnerability involves setting `$wgManageWiki['namespaces'] = false;`.","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":"ManageWiki has SQL injection vulnerability in NamespaceMigrationJob","id":"CVE-2025-32956","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"baserCMS: unsafe File Upload Leading to Remote Code Execution (RCE)","id":"CVE-2025-32957"},"packages":[],"prev":{"headline":"Harden-Runner Evasion of 'disable-sudo' policy","id":"CVE-2025-32955"},"products":["ManageWiki"],"published":"2025-04-21","related":[{"cvss_score":9.4,"headline":"wikiconfig API leaked private config variables set through ManageWiki","id":"CVE-2021-29483","kev_date_added":null,"published":"2021-04-28"},{"cvss_score":6.5,"headline":"Cross-Site Scripting in the extensions, settings, permissions and namespaces subpages of ManageWiki","id":"CVE-2024-25109","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":4.6,"headline":"Missing authorization in ManageWiki","id":"CVE-2025-32964","kev_date_added":null,"published":"2025-04-22"},{"cvss_score":4.4,"headline":"ManageWiki Vulnerable to Self-XSS in review dialog via unsanitized field reflection","id":"CVE-2025-43861","kev_date_added":null,"published":"2025-04-24"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-12","vendors":["miraheze"]},"summary":"Attackers can inject SQL commands via namespace renaming in ManageWiki, potentially reading or modifying database content.","url":"https://insights.sbomify.com/CVE-2025-32956/"}