{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-40373 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-40373 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-40373 is a critical code injection vulnerability in n/a, published on 10 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-40373 and fix it if it is affected.\n\nWhat it is: CVE-2021-40373 is a critical code injection vulnerability in n/a, published on 10 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-40373 in the wild and no public exploit code.\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-2021-40373/ (Markdown: https://insights.sbomify.com/CVE-2021-40373/index.md)","id":"CVE-2021-40373","markdown":"https://insights.sbomify.com/CVE-2021-40373/index.md","name":"CVE-2021-40373","record":{"aliases":["GHSA-qmpc-fmq6-gf8j"],"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":"Attackers can execute arbitrary PHP code by injecting it into the core configuration page of playSMS.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"playsms","vendor":"playsms"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"playSMS before 1.4.5 allows Arbitrary Code Execution by entering PHP code at the #tabs-information-page of core_main_config, and then executing that code via the index.php?app=main\u0026inc=core_welcome URI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-08-31","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-08-31T13:03:10Z","kind":"github_poc","ref":"https://github.com/maikroservice/CVE-2021-40373","stars":1,"title":"CVE-2021-40373 - remote code execution"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2021-40373","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-40374"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2021-40371"},"products":["n/a"],"published":"2021-09-10","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":"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary PHP code by injecting it into the core configuration page of playSMS.","url":"https://insights.sbomify.com/CVE-2021-40373/"}