{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-0508 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2011-0508 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-0508 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-0508 and fix it if it is affected.\n\nWhat it is: CVE-2011-0508 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Jan 2011. 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-2011-0508 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-2011-0508/ (Markdown: https://insights.sbomify.com/CVE-2011-0508/index.md)","id":"CVE-2011-0508","markdown":"https://insights.sbomify.com/CVE-2011-0508/index.md","name":"CVE-2011-0508","record":{"aliases":["GHSA-gfg7-fg26-2g7j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Contao CMS","requires_auth":"none","summary":"Remote attackers can inject arbitrary web script or HTML via the X_FORWARDED_FOR header in Contao CMS comments, potentially compromising user sessions.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"contao_cms","vendor":"contao"}],"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":"Cross-site scripting (XSS) vulnerability in system/modules/comments/Comments.php in Contao CMS 2.9.2, and possibly other versions before 2.9.3, allows remote attackers to inject arbitrary web script or HTML via the HTTP X_FORWARDED_FOR header, which is stored by system/libraries/Environment.php but not properly handled by a comments action to main.php.","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":"Cross-site scripting in n/a","id":"CVE-2011-0508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2011"},"n_packages":0,"n_references":7,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2011-0509"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2011-0507"},"products":["n/a"],"published":"2011-01-20","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2014-1860","kev_date_added":null,"published":"2020-01-08"},{"cvss_score":9.8,"headline":"Contao SQL injection in the backend and listing module","id":"CVE-2017-16558","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":9.8,"headline":"Contao Does Not Invalidate Existing Sessions When Password Changes","id":"CVE-2019-10641","kev_date_added":null,"published":"2019-04-17"},{"cvss_score":9.8,"headline":"Contao Does Not Expire Tokens Correctly","id":"CVE-2019-10643","kev_date_added":null,"published":"2019-04-17"},{"cvss_score":8.8,"headline":"Contao CSRF Token Bypass","id":"CVE-2019-10642","kev_date_added":null,"published":"2019-04-17"},{"cvss_score":8.8,"headline":"Contao Core directory traversal vulnerability","id":"CVE-2017-10993","kev_date_added":null,"published":"2017-07-21"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2012-1297","kev_date_added":null,"published":"2012-03-19"}],"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-08-06","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary web script or HTML via the X_FORWARDED_FOR header in Contao CMS comments, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2011-0508/"}