{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16604 is a high-severity code injection vulnerability in n/a, published on 6 Sep 2018. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16604 and fix it if it is affected.\n\nWhat it is: CVE-2018-16604 is a high-severity code injection vulnerability in n/a, published on 6 Sep 2018. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-16604 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-16604/ (Markdown: https://insights.sbomify.com/CVE-2018-16604/index.md)","id":"CVE-2018-16604","markdown":"https://insights.sbomify.com/CVE-2018-16604/index.md","name":"CVE-2018-16604","record":{"aliases":["GHSA-q7mm-h7vg-6554"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Nibbleblog CMS","requires_auth":"high_privilege","summary":"An authenticated attacker can execute arbitrary PHP code by injecting payloads into the username field due to improper handling of double quotes.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nibbleblog","vendor":"nibbleblog"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/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":"An issue was discovered in Nibbleblog v4.0.5. With an admin's username and password, an attacker can execute arbitrary PHP code by changing the username because the username is surrounded by double quotes (e.g., \"${phpinfo()}\").","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":"Code injection in n/a","id":"CVE-2018-16604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-16605"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-16603"},"products":["n/a"],"published":"2018-09-06","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2019-7719","kev_date_added":null,"published":"2019-02-11"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2020-23356","kev_date_added":null,"published":"2021-01-27"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-6966","kev_date_added":null,"published":"2015-09-16"},{"cvss_score":6.5,"headline":"File upload in n/a","id":"CVE-2015-6967","kev_date_added":null,"published":"2015-09-16"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2018-6470","kev_date_added":null,"published":"2018-02-01"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2014-8996","kev_date_added":null,"published":"2014-11-20"}],"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":"An authenticated attacker can execute arbitrary PHP code by injecting payloads into the username field due to improper handling of double quotes.","url":"https://insights.sbomify.com/CVE-2018-16604/"}