{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8880 exists.","fix":"No fix has been published for CVE-2024-8880 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-8880 is a medium-severity code injection vulnerability in playSMS, published on 16 Sep 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-8880 and fix it if it is affected.\n\nWhat it is: CVE-2024-8880 is a medium-severity code injection vulnerability in playSMS, published on 16 Sep 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-8880 exists.\n\nAffected product: playSMS. 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-8880/ (Markdown: https://insights.sbomify.com/CVE-2024-8880/index.md)","id":"CVE-2024-8880","markdown":"https://insights.sbomify.com/CVE-2024-8880/index.md","name":"CVE-2024-8880","record":{"aliases":["GHSA-h478-hrvj-hrjq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"playSMS web application","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via code injection in the playSMS template handler, requiring high complexity and permissions.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"playsms","vendor":"playsms"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"A vulnerability classified as critical has been found in playSMS 1.4.4/1.4.5/1.4.6/1.4.7. Affected is an unknown function of the file /playsms/index.php?app=main\u0026inc=core_auth\u0026route=forgot\u0026op=forgot of the component Template Handler. The manipulation of the argument username/email/captcha leads to code injection. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component. The project maintainer was informed early about the issue. Investigation shows that playSMS up to 1.4.3 contained a fix but later versions re-introduced the flaw. As long as the latest version of the playsms/tpl package is used, the software is not affected. Version \u003e=1.4.4 shall fix this issue for sure.","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":"playSMS Template index.php code injection","id":"CVE-2024-8880","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in GS1900-48 firmware","id":"CVE-2024-8881"},"packages":[],"prev":{"headline":"Unauthenticated Password Reset","id":"CVE-2024-8878"},"products":["playSMS"],"published":"2024-09-16","related":[{"cvss_score":9.8,"headline":"PlaySMS Server-Side Template Injection","id":"CVE-2020-8644","kev_date_added":"2021-11-03","published":"2020-02-05"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-47034","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-40373","kev_date_added":null,"published":"2021-09-10"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2017-9101","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2017-9080","kev_date_added":null,"published":"2017-05-19"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2008-5881","kev_date_added":null,"published":"2009-01-09"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2009-0103","kev_date_added":null,"published":"2009-01-09"}],"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-09-16","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via code injection in the playSMS template handler, requiring high complexity and permissions.","url":"https://insights.sbomify.com/CVE-2024-8880/"}