# DRUPAL-CONTRIB-2023-006: This module enables you to add social sharing buttons to a site.

> Insufficient sanitization in Drupal social sharing module allows high-privilege attackers to inject scripts via configuration fields.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Mar 2023

## What is DRUPAL-CONTRIB-2023-006?

DRUPAL-CONTRIB-2023-006 is a cross-site scripting vulnerability in drupal/better_social_sharing_buttons, published on 1 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

This module enables you to add social sharing buttons to a site.

The module doesn't sufficiently sanitize the weight and ratio values entered in the module or block configuration.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer blocks".

## Which versions are affected by DRUPAL-CONTRIB-2023-006?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/better_social_sharing_buttons` | Packagist:https://packages.drupal.org/8 | All versions | 4.0.3 |

## How do I fix DRUPAL-CONTRIB-2023-006?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2023-006 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2023-006 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2023-006 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2023-006 is a cross-site scripting vulnerability in drupal/better_social_sharing_buttons, published on 1 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2023-006 in the wild and no public exploit code.

Affected product: drupal/better_social_sharing_buttons. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-006/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-006/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2023-006

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-006/
Summaries are generated and may contain mistakes; the official description above is the record.