{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63551 exists.","fix":"No fix has been published for CVE-2025-63551 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63551 is a high-severity vulnerability in Metinfo Metinfo, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-63551 and fix it if it is affected.\n\nWhat it is: CVE-2025-63551 is a high-severity vulnerability in Metinfo Metinfo, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63551 exists.\n\nAffected product: Metinfo Metinfo. 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-63551/ (Markdown: https://insights.sbomify.com/CVE-2025-63551/index.md)","id":"CVE-2025-63551","markdown":"https://insights.sbomify.com/CVE-2025-63551/index.md","name":"CVE-2025-63551","record":{"aliases":["GHSA-2pmp-x7wc-gxr9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MetInfo CMS","requires_auth":"none","summary":"An attacker can exploit an XML parsing flaw in MetInfo CMS to perform Server-Side Request Forgery, enabling internal network reconnaissance and sensitive data retrieval.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"metinfo","vendor":"metinfo"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"A Server-Side Request Forgery (SSRF) vulnerability, achievable through an XML External Entity (XXE) injection, exists in MetInfo Content Management System (CMS) thru 8.1. This flaw stems from a defect in the XML parsing logic, which allows an attacker to construct a malicious XML entity that forces the server to initiate an HTTP request to an arbitrary internal or external network address. Successful exploitation could lead to internal network reconnaissance, port scanning, or the retrieval of sensitive information. The vulnerability may be present in the backend API called by or associated with the path `/admin/#/webset/?head_tab_active=0`, where user-provided XML data is processed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"XML external entity in n/a","id":"CVE-2025-63551","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"metinfo:metinfo","products":["metinfo:metinfo"],"type":"xxe","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-63560"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-63548"},"products":["n/a"],"published":"2025-11-06","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-22295","kev_date_added":null,"published":"2022-02-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-23335","kev_date_added":null,"published":"2022-02-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-21127","kev_date_added":null,"published":"2021-09-15"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-19305","kev_date_added":null,"published":"2021-08-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-18175","kev_date_added":null,"published":"2021-07-29"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-21132","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-21133","kev_date_added":null,"published":"2021-07-12"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-07","vendors":["n/a"]},"summary":"An attacker can exploit an XML parsing flaw in MetInfo CMS to perform Server-Side Request Forgery, enabling internal network reconnaissance and sensitive data retrieval.","url":"https://insights.sbomify.com/CVE-2025-63551/"}