# DRUPAL-CONTRIB-2019-058: This module enables you to customize meta tags to help with a site's search engine ranking and improve the display of page summaries when sh

> An attacker can bypass maintenance mode restrictions to access restricted content if the site is configured to disallow access to certain content.

- **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:** 24 Jul 2019

## What is DRUPAL-CONTRIB-2019-058?

DRUPAL-CONTRIB-2019-058 is a vulnerability in drupal/metatag, published on 24 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module enables you to customize meta tags to help with a site's search engine ranking and improve the display of page summaries when shared on social networks.

The module doesn't sufficiently check for a site being in maintenance mode.

This vulnerability is mitigated by the fact that the site must be configured to disallow access to certain content, and must be put into maintenance mode.

## Which versions are affected by DRUPAL-CONTRIB-2019-058?


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

## How do I fix DRUPAL-CONTRIB-2019-058?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2019-058 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-058 is a vulnerability in drupal/metatag, published on 24 Jul 2019. 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-2019-058 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2019-058

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