{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19463 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19463 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19463 is a high-severity vulnerability in n/a, published on 22 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19463 and fix it if it is affected.\n\nWhat it is: CVE-2018-19463 is a high-severity vulnerability in n/a, published on 22 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-19463 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-2018-19463/ (Markdown: https://insights.sbomify.com/CVE-2018-19463/index.md)","id":"CVE-2018-19463","markdown":"https://insights.sbomify.com/CVE-2018-19463/index.md","name":"CVE-2018-19463","record":{"aliases":["GHSA-87q4-fqr2-3wr2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Z-BlogPHP CMS","requires_auth":"low_privilege","summary":"Authenticated attackers can execute arbitrary PHP code by uploading a malicious file disguised as an image in Z-BlogPHP.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"z-blogphp","vendor":"zblogcn"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"zb_system/function/lib/upload.php in Z-BlogPHP through 1.5.1 allows remote attackers to execute arbitrary PHP code by using the image/jpeg content type in an upload to the zb_system/admin/index.php?act=UploadMng URI. NOTE: The vendor's position is \"We have no dynamic including. No one can run PHP by uploading an image in current version.\" It also requires authentication","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-2018-19463","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19464"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2018-19462"},"products":["n/a"],"published":"2018-11-22","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-55529","kev_date_added":null,"published":"2025-01-06"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-40357","kev_date_added":null,"published":"2022-09-20"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2020-29177","kev_date_added":null,"published":"2021-12-02"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-18842","kev_date_added":null,"published":"2018-10-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-8893","kev_date_added":null,"published":"2018-03-31"},{"cvss_score":7.8,"headline":"File upload in n/a","id":"CVE-2020-29176","kev_date_added":null,"published":"2021-12-02"}],"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 attackers can execute arbitrary PHP code by uploading a malicious file disguised as an image in Z-BlogPHP.","url":"https://insights.sbomify.com/CVE-2018-19463/"}