{"answers":{"affected":"2 open source packages ship an affected version, including anchorcms/anchor-cms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-7251 exists.","fix":"Upgrade anchorcms/anchor-cms to 0.12.7 or later.","what":"CVE-2018-7251 is a critical vulnerability in n/a, published on 19 Feb 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-7251 and fix it if it is affected.\n\nWhat it is: CVE-2018-7251 is a critical vulnerability in n/a, published on 19 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-7251 exists.\n\nAffected packages and fixed versions:\n- anchorcms/anchor-cms (Packagist): affected all versions; fixed in 0.12.7\n- anchorcms/anchor-cms (Packagist): affected all versions; fixed in 0.12.7\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-7251/ (Markdown: https://insights.sbomify.com/CVE-2018-7251/index.md)","id":"CVE-2018-7251","markdown":"https://insights.sbomify.com/CVE-2018-7251/index.md","name":"CVE-2018-7251","record":{"aliases":["GHSA-hxcw-pqqc-rv85"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Anchor CMS","requires_auth":"none","summary":"Attackers can access exposed error logs containing MySQL credentials, leading to potential database compromise.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anchor","vendor":"anchorcms"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in config/error.php in Anchor 0.12.3. The error log is exposed at an errors.log URI, and contains MySQL credentials if a MySQL error (such as \"Too many connections\") has occurred.","ecosystems":["Packagist"],"exploits":{"exploitdb":1,"first_seen":"2019-10-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":"2019-10-03","kind":"exploitdb","ref":"47459","stars":null,"title":"AnchorCMS \u003c 0.12.3a - Information Disclosure"},{"date":null,"kind":"nuclei","ref":"http/cves/2018/CVE-2018-7251.yaml","stars":null,"title":"Anchor CMS 0.12.3 - Error Log Exposure"}],"tier":"weaponised"},"has_fix":true,"headline":"Anchor CMS Logs Credentials","id":"CVE-2018-7251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":2,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-7253"},"packages":[{"ecosystem":"Packagist","fixed":["0.12.7"],"introduced":["0"],"last_affected":[],"package":"anchorcms/anchor-cms","purl":null,"source":"GHSA-hxcw-pqqc-rv85"},{"ecosystem":"Packagist","fixed":["0.12.7"],"introduced":["0"],"last_affected":[],"package":"anchorcms/anchor-cms","purl":"pkg:composer/anchorcms/anchor-cms","source":"GHSA-hxcw-pqqc-rv85"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-7250"},"products":["n/a"],"published":"2018-02-19","related":[{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2020-12071","kev_date_added":null,"published":"2020-04-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can access exposed error logs containing MySQL credentials, leading to potential database compromise.","url":"https://insights.sbomify.com/CVE-2018-7251/"}