# DRUPAL-CONTRIB-2023-018: This module provides social media share & follow buttons.

> An attacker can read node labels without proper access checks if the node ID is exposed via route parameters in specific configurations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 May 2023

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

DRUPAL-CONTRIB-2023-018 is a missing authorization vulnerability in drupal/addtoany, published on 31 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module provides social media share & follow buttons.

The module doesn't sufficiently check access to a node when retrieving the label of an AddToAny block.

This vulnerability is mitigated by the fact it requires the node ID to be passed via the route, requiring another module or specific configuration to provide this ID, as the /node/{id} page doesn't provide this value on an access denied.

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/addtoany` | Packagist:https://packages.drupal.org/8 | All versions | 1.21.0, 2.0.4 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2023-018 is a missing authorization vulnerability in drupal/addtoany, published on 31 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2023-018 in the wild and no public exploit code.

Affected product: drupal/addtoany. 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-018/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-018/index.md)
```

## Sources

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

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