# DRUPAL-CONTRIB-2023-049: This module enables you to view all paragraph entities in an admin view.

> Non-admin users can bypass access controls to view all paragraph entities in an admin view, exposing sensitive data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Nov 2023

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

DRUPAL-CONTRIB-2023-049 is a missing authorization vulnerability in drupal/paragraphs_admin, published on 1 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module enables you to view all paragraph entities in an admin view.  
The module contains an access bypass that allows non admin users to access the view.  
The vulnerability can be mitigated by editing the view to change the permission required to access the page.

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


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

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

Change a configuration setting.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2023-049 is a missing authorization vulnerability in drupal/paragraphs_admin, published on 1 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2023-049 in the wild and no public exploit code.

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

## Sources

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

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