{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17575 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17575 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17575 is a high-severity vulnerability in n/a, published on 14 Oct 2019. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-17575 and fix it if it is affected.\n\nWhat it is: CVE-2019-17575 is a high-severity vulnerability in n/a, published on 14 Oct 2019. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-17575 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-17575/ (Markdown: https://insights.sbomify.com/CVE-2019-17575/index.md)","id":"CVE-2019-17575","markdown":"https://insights.sbomify.com/CVE-2019-17575/index.md","name":"CVE-2019-17575","record":{"aliases":["GHSA-m48x-5wvq-wmqg"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WBCE CMS","requires_auth":"high_privilege","summary":"Authenticated admins can bypass file rename filters to upload and execute arbitrary PHP code via crafted filenames.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wbce_cms","vendor":"wbce"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"A file-rename filter bypass exists in admin/media/rename.php in WBCE CMS 1.4.0 and earlier. This can be exploited by an authenticated user with admin privileges to rename a media filename and extension. (For example: place PHP code in a .jpg file, and then change the file's base name to filename.ph and change the file's extension to p. Because of concatenation, the name is then treated as filename.php.) At the result, remote attackers can execute arbitrary PHP code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2019-17575","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":"Dolibarr Cross-site Scripting via outgoing email setup feature","id":"CVE-2019-17576"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-17574"},"products":["n/a"],"published":"2019-10-14","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-39796","kev_date_added":null,"published":"2023-11-10"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-46020","kev_date_added":null,"published":"2022-12-20"},{"cvss_score":9.8,"headline":"SQL Injection in wbce/wbce_cms","id":"CVE-2021-3817","kev_date_added":null,"published":"2021-12-09"},{"cvss_score":9.4,"headline":"WBCE CMS is Vulnerable to Time-Based Blind SQL Injection through groups[] Parameter","id":"CVE-2025-65950","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":9.1,"headline":"WBCE CMS has Weak Random Number Generator in Password Generation Function","id":"CVE-2025-67504","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":8.7,"headline":"WBCE CMS 1.5.2 - Remote Code Execution (RCE) (Authenticated)","id":"CVE-2022-50936","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.7,"headline":"WBCE CMS 1.6.2 Remote Code Execution via Elfinder File Upload","id":"CVE-2024-58283","kev_date_added":null,"published":"2025-12-10"}],"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-08-05","vendors":["n/a"]},"summary":"Authenticated admins can bypass file rename filters to upload and execute arbitrary PHP code via crafted filenames.","url":"https://insights.sbomify.com/CVE-2019-17575/"}