{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6251 exists.","fix":"No fix has been published for CVE-2024-6251 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6251 is a medium-severity cross-site scripting vulnerability in playSMS, published on 22 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-6251 and fix it if it is affected.\n\nWhat it is: CVE-2024-6251 is a medium-severity cross-site scripting vulnerability in playSMS, published on 22 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6251 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-6251/ (Markdown: https://insights.sbomify.com/CVE-2024-6251/index.md)","id":"CVE-2024-6251","markdown":"https://insights.sbomify.com/CVE-2024-6251/index.md","name":"CVE-2024-6251","record":{"aliases":["GHSA-3m77-f49c-p58r"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"playSMS web application","requires_auth":"high_privilege","summary":"Attackers can inject malicious scripts via the phonebook name or email fields in playSMS, potentially compromising user sessions.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"playsms","vendor":"playsms"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"}],"description":"A vulnerability, which was classified as problematic, was found in playSMS 1.4.3. Affected is an unknown function of the file /index.php?app=main\u0026inc=feature_phonebook\u0026op=phonebook_list of the component New Phonebook Handler. The manipulation of the argument name/email leads to basic cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-269418 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.","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 New Phonebook cross site scripting","id":"CVE-2024-6251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Zorlan SkyCaiji Task cross site scripting","id":"CVE-2024-6252"},"packages":[],"prev":{"headline":"Absolute Path Traversal in parisneo/lollms-webui","id":"CVE-2024-6250"},"products":["playSMS"],"published":"2024-06-22","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-08-01","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts via the phonebook name or email fields in playSMS, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2024-6251/"}