# DRUPAL-CONTRIB-2023-013: This module enables you to secure any page with a password.

> The Drupal password-protect module fails to restrict access to protected page content, exposing it to unauthorized users.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 12 Apr 2023

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

DRUPAL-CONTRIB-2023-013 is a missing authorization vulnerability in drupal/protected_pages, published on 12 Apr 2023. It can be exploited over the network, with no action from the victim.

### Official description

This module enables you to secure any page with a password.

The module does not sufficiently restrict access to the page content.

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

No fix published yet.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2023-013 is a missing authorization vulnerability in drupal/protected_pages, published on 12 Apr 2023. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2023-013 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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