{"answers":{"affected":"2 open source packages ship an affected version, including Piranha. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55342 exists.","fix":"No fix has been published for CVE-2024-55342 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-55342 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-55342 and fix it if it is affected.\n\nWhat it is: CVE-2024-55342 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55342 exists.\n\nAffected packages and fixed versions:\n- Piranha (NuGet): affected all versions up to 11.1.0; no fix listed\n- Piranha (NuGet): affected all versions up to 11.1.0; no fix listed\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-55342/ (Markdown: https://insights.sbomify.com/CVE-2024-55342/index.md)","id":"CVE-2024-55342","markdown":"https://insights.sbomify.com/CVE-2024-55342/index.md","name":"CVE-2024-55342","record":{"aliases":["GHSA-cmwp-442x-3rcv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Piranha CMS","requires_auth":"none","summary":"Authenticated attackers can upload malicious PDFs to trigger XSS in victim browsers, potentially leading to code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"piranha_cms","vendor":"dotnetfoundation"}],"cvss":{"score":4.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A file upload functionality in Piranha CMS 11.1 allows authenticated remote attackers to upload a crafted PDF file to /manager/media. This PDF can contain malicious JavaScript code, which is executed when a victim user opens or interacts with the PDF in their web browser, leading to a XSS vulnerability.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Piranha CMS Cross-site Scripting vulnerability","id":"CVE-2024-55342","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Security feature bypass in Lucee Server","id":"CVE-2024-55354"},"packages":[{"ecosystem":"NuGet","fixed":[],"introduced":["0"],"last_affected":["11.1.0"],"package":"Piranha","purl":null,"source":"GHSA-cmwp-442x-3rcv"},{"ecosystem":"NuGet","fixed":[],"introduced":["0"],"last_affected":["11.1.0"],"package":"Piranha","purl":"pkg:nuget/Piranha","source":"GHSA-cmwp-442x-3rcv"}],"prev":{"headline":"Piranha CMS Cross-site Scripting vulnerability","id":"CVE-2024-55341"},"products":["n/a"],"published":"2024-12-20","related":[{"cvss_score":8.1,"headline":"Piranha CMS - Site-wide Cross-Site Request Forgery (CSRF)","id":"CVE-2021-25976","kev_date_added":null,"published":"2021-11-16"},{"cvss_score":6.8,"headline":"PiranhaCMS stored XSS","id":"CVE-2025-57692","kev_date_added":null,"published":"2025-09-26"},{"cvss_score":6.1,"headline":"Piranha has stored cross-site scripting (XSS) vulnerability","id":"CVE-2025-67290","kev_date_added":null,"published":"2025-12-22"},{"cvss_score":6.1,"headline":"Piranha has stored cross-site scripting (XSS) vulnerability","id":"CVE-2025-67291","kev_date_added":null,"published":"2025-12-22"},{"cvss_score":6.1,"headline":"Piranha CMS vulnerable to stored cross-site scripting (XSS)","id":"CVE-2025-61413","kev_date_added":null,"published":"2025-10-23"},{"cvss_score":5.4,"headline":"Piranha CMS - Stored XSS in Page Title","id":"CVE-2021-25977","kev_date_added":null,"published":"2021-10-25"},{"cvss_score":4.7,"headline":"Piranha CMS Cross-site Scripting vulnerability","id":"CVE-2024-55341","kev_date_added":null,"published":"2024-12-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-12-20","vendors":["n/a"]},"summary":"Authenticated attackers can upload malicious PDFs to trigger XSS in victim browsers, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2024-55342/"}