{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-3837 exists.","fix":"No fix has been published for CVE-2012-3837 yet. Limit exposure of the affected software until one is available.","what":"CVE-2012-3837 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Jul 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2012-3837 and fix it if it is affected.\n\nWhat it is: CVE-2012-3837 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Jul 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-3837 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-2012-3837/ (Markdown: https://insights.sbomify.com/CVE-2012-3837/index.md)","id":"CVE-2012-3837","markdown":"https://insights.sbomify.com/CVE-2012-3837/index.md","name":"CVE-2012-3837","record":{"aliases":["GHSA-2223-xwpw-4pw3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Baby Gekko web app","requires_auth":"none","summary":"Remote attackers can inject arbitrary web script or HTML via multiple registration parameters in Baby Gekko, requiring user interaction to execute.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"baby_gekko","vendor":"babygekko"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Multiple cross-site scripting (XSS) vulnerabilities in apps/users/registration.template.php in Baby Gekko 1.2.0 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) username, (2) email_address, (3) password, (4) password_verify, (5) firstname, (6) lastname, or (7) verification_code parameter to users/action/register.  NOTE: some of these details are obtained from third party information.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2012-05-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2012-05-03","kind":"exploitdb","ref":"18827","stars":null,"title":"Baby Gekko CMS 1.1.5c - Multiple Persistent Cross-Site Scripting Vulnerabilities"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2012-3837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2012"},"n_packages":0,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2012-3838"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2012-3836"},"products":["n/a"],"published":"2012-07-03","related":[{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2012-3838","kev_date_added":null,"published":"2012-07-03"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2012-5700","kev_date_added":null,"published":"2014-09-22"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2012-3836","kev_date_added":null,"published":"2012-07-03"}],"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"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary web script or HTML via multiple registration parameters in Baby Gekko, requiring user interaction to execute.","url":"https://insights.sbomify.com/CVE-2012-3837/"}