{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11369 is a critical SQL injection vulnerability in n/a, published on 22 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11369 and fix it if it is affected.\n\nWhat it is: CVE-2018-11369 is a critical SQL injection vulnerability in n/a, published on 22 May 2018. 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-2018-11369 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-11369/ (Markdown: https://insights.sbomify.com/CVE-2018-11369/index.md)","id":"CVE-2018-11369","markdown":"https://insights.sbomify.com/CVE-2018-11369/index.md","name":"CVE-2018-11369","record":{"aliases":["GHSA-2f5r-9f46-7fh6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PbootCMS","requires_auth":"none","summary":"Attackers can exploit SQL injection in PbootCMS to retrieve sensitive database information via the scode parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pbootcms","vendor":"pbootcms"}],"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-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"An issue was discovered in PbootCMS v1.0.9. There is a SQL Injection that can get important information from the database via the \\apps\\home\\controller\\ParserController.php scode parameter.","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":"SQL injection in n/a","id":"CVE-2018-11369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-11371"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-11367"},"products":["n/a"],"published":"2018-05-22","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-39834","kev_date_added":null,"published":"2023-08-24"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-37497","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-32417","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-23580","kev_date_added":null,"published":"2021-07-08"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-16356","kev_date_added":null,"published":"2020-03-02"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-16357","kev_date_added":null,"published":"2020-03-02"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-19893","kev_date_added":null,"published":"2018-12-06"}],"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-17","vendors":["n/a"]},"summary":"Attackers can exploit SQL injection in PbootCMS to retrieve sensitive database information via the scode parameter.","url":"https://insights.sbomify.com/CVE-2018-11369/"}