{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-3810 exists.","fix":"No fix has been published for CVE-2018-3810 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3810 is a critical authentication bypass vulnerability in n/a, published on 1 Jan 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-3810 and fix it if it is affected.\n\nWhat it is: CVE-2018-3810 is a critical authentication bypass vulnerability in n/a, published on 1 Jan 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-3810 exists.\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-3810/ (Markdown: https://insights.sbomify.com/CVE-2018-3810/index.md)","id":"CVE-2018-3810","markdown":"https://insights.sbomify.com/CVE-2018-3810/index.md","name":"CVE-2018-3810","record":{"aliases":["GHSA-f59r-v67m-78wf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary JavaScript or HTML into all WordPress pages via the Oturia Smart Google Code Inserter plugin due to missing authorization checks.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smart_google_code_inserter","vendor":"oturia"}],"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-287","name":"Improper Authentication"}],"description":"Authentication Bypass vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attackers to insert arbitrary JavaScript or HTML code (via the sgcgoogleanalytic parameter) that runs on all pages served by WordPress. The saveGoogleCode() function in smartgooglecode.php does not check if the current request is made by an authorized user, thus allowing any unauthenticated user to successfully update the inserted code.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-01-03","github_poc":3,"max_poc_stars":1,"metasploit":0,"nuclei":1,"refs":[{"date":"2021-07-30T10:06:04Z","kind":"github_poc","ref":"https://github.com/nth347/CVE-2018-3810_exploit","stars":1,"title":"Exploit for CVE-2018-3810"},{"date":"2018-01-03","kind":"exploitdb","ref":"43420","stars":null,"title":"WordPress Plugin Smart Google Code Inserter \u003c 3.5 - Authentication Bypass / SQL Injection"},{"date":"2018-03-29T14:04:11Z","kind":"github_poc","ref":"https://github.com/lucad93/CVE-2018-3810","stars":0,"title":null},{"date":"2019-02-02T21:19:32Z","kind":"github_poc","ref":"https://github.com/cved-sources/cve-2018-3810","stars":0,"title":"cve-2018-3810"},{"date":null,"kind":"nuclei","ref":"http/cves/2018/CVE-2018-3810.yaml","stars":null,"title":"Oturia WordPress Smart Google Code Inserter \u003c3.5 - Authentication Bypass"}],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2018-3810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2018-3811"},"packages":[],"prev":{"headline":"Information Exposure on Case Insensitive File Systems in serve","id":"CVE-2018-3809"},"products":["n/a"],"published":"2018-01-01","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-3811","kev_date_added":null,"published":"2018-01-01"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can inject arbitrary JavaScript or HTML into all WordPress pages via the Oturia Smart Google Code Inserter plugin due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2018-3810/"}