{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27563 exists.","fix":"No fix has been published for CVE-2024-27563 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-27563 is a medium-severity server-side request forgery vulnerability in n/a, published on 5 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-27563 and fix it if it is affected.\n\nWhat it is: CVE-2024-27563 is a medium-severity server-side request forgery vulnerability in n/a, published on 5 Mar 2024. 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-2024-27563 exists.\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-2024-27563/ (Markdown: https://insights.sbomify.com/CVE-2024-27563/index.md)","id":"CVE-2024-27563","markdown":"https://insights.sbomify.com/CVE-2024-27563/index.md","name":"CVE-2024-27563","record":{"aliases":["GHSA-vqjx-886g-c3rv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WonderCMS","requires_auth":"none","summary":"Attackers can force WonderCMS to make arbitrary requests via crafted URLs in the pluginThemeUrl parameter, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wondercms","vendor":"wondercms"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A Server-Side Request Forgery (SSRF) in the getFileFromRepo function of WonderCMS v3.1.3 allows attackers to force the application to make arbitrary requests via injection of crafted URLs into the pluginThemeUrl parameter.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Server-side request forgery in n/a","id":"CVE-2024-27563","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in mm1.ltd source code","id":"CVE-2024-27564"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2024-27561"},"products":["n/a"],"published":"2024-03-05","related":[{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2020-35313","kev_date_added":null,"published":"2021-04-20"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-35314","kev_date_added":null,"published":"2021-04-20"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2014-8704","kev_date_added":null,"published":"2017-03-17"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2014-8705","kev_date_added":null,"published":"2017-03-17"},{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2024-32340","kev_date_added":null,"published":"2024-04-17"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2024-27561","kev_date_added":null,"published":"2024-03-05"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2018-14387","kev_date_added":null,"published":"2018-07-18"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-29","vendors":["n/a"]},"summary":"Attackers can force WonderCMS to make arbitrary requests via crafted URLs in the pluginThemeUrl parameter, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2024-27563/"}