{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-8908 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-8908 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-8908 is a critical vulnerability in n/a, published on 18 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-8908 and fix it if it is affected.\n\nWhat it is: CVE-2019-8908 is a critical vulnerability in n/a, published on 18 Feb 2019. 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-2019-8908 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-2019-8908/ (Markdown: https://insights.sbomify.com/CVE-2019-8908/index.md)","id":"CVE-2019-8908","markdown":"https://insights.sbomify.com/CVE-2019-8908/index.md","name":"CVE-2019-8908","record":{"aliases":["GHSA-26gh-p63x-8w5r"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WTCMS","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code by uploading a malicious image file with a PHP extension in the email template settings.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wtcms","vendor":"wtcms_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"An issue was discovered in WTCMS 1.0. It allows remote attackers to execute arbitrary PHP code by going to the \"Setting -\u003e Mailbox configuration -\u003e Registration email template\" screen, and uploading an image file, as demonstrated by a .php filename and the \"Content-Type: image/gif\" header.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2019-8908","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-8909"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-8907"},"products":["n/a"],"published":"2019-02-18","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-48237","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-8910","kev_date_added":null,"published":"2019-02-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-10267","kev_date_added":null,"published":"2018-04-21"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-8909","kev_date_added":null,"published":"2019-02-18"},{"cvss_score":6.9,"headline":"taosir WTCMS SlideController SlideController.class.php delete sql injection","id":"CVE-2025-13782","kev_date_added":null,"published":"2025-11-30"},{"cvss_score":6.9,"headline":"taosir WTCMS index.php fetch code injection","id":"CVE-2025-13786","kev_date_added":null,"published":"2025-11-30"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary PHP code by uploading a malicious image file with a PHP extension in the email template settings.","url":"https://insights.sbomify.com/CVE-2019-8908/"}