{"answers":{"affected":"","exploited":"There is no known exploitation of DRUPAL-CONTRIB-2020-002 in the wild and no public exploit code.","fix":"No fix has been published for DRUPAL-CONTRIB-2020-002 yet. Limit exposure of the affected software until one is available.","what":"DRUPAL-CONTRIB-2020-002 is a cross-site scripting vulnerability in drupal/spamspan, published on 22 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for DRUPAL-CONTRIB-2020-002 and fix it if it is affected.\n\nWhat it is: DRUPAL-CONTRIB-2020-002 is a cross-site scripting vulnerability in drupal/spamspan, published on 22 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of DRUPAL-CONTRIB-2020-002 in the wild and no public exploit code.\n\nAffected product: drupal/spamspan. 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/DRUPAL-CONTRIB-2020-002/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2020-002/index.md)","id":"DRUPAL-CONTRIB-2020-002","markdown":"https://insights.sbomify.com/DRUPAL-CONTRIB-2020-002/index.md","name":"DRUPAL-CONTRIB-2020-002","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Drupal SpamSpan module","requires_auth":"low_privilege","summary":"An attacker can inject malicious scripts via unsanitized HTML in the SpamSpan Twig filter if custom templates are used, potentially leading to XSS.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The SpamSpan module obfuscates email addresses to help prevent spambots from collecting them.\n\nThis module contains a spamspan twig filter which doesn't sanitize the passed HTML string.\n\nThis vulnerability is mitigated by the fact that sites must have custom twig template files that use the SpamSpan filter on a field that an attacker could populate. By default the SpamSpan module does not use the vulnerable twig filter.","ecosystems":["Packagist:https://packages.drupal.org/8"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"The SpamSpan module obfuscates email addresses to help prevent spambots from collecting them.","id":"DRUPAL-CONTRIB-2020-002","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Packagist:https://packages.drupal.org/8","fixed":[],"introduced":["1.0.0"],"last_affected":["1.0.0"],"package":"drupal/spamspan","purl":"pkg:composer/drupal/spamspan?repository_url=https:%2F%2Fpackages.drupal.org%2F8","source":"DRUPAL-CONTRIB-2020-002"}],"products":null,"published":"2020-01-22","related":[],"sources":[{"class":"attribution","licence":"MIT","name":"Drupal","prefix":"DRUPAL"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can inject malicious scripts via unsanitized HTML in the SpamSpan Twig filter if custom templates are used, potentially leading to XSS.","url":"https://insights.sbomify.com/DRUPAL-CONTRIB-2020-002/"}