# DRUPAL-CONTRIB-2018-002: The Node view permissions module enables the "View own content" and "View any content" permissions for each content type on the permissions page.

> Authenticated users with view permissions can access unpublished content they are not authorized to see in the Node view permissions module.

- **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:** 10 Jan 2018

## What is DRUPAL-CONTRIB-2018-002?

DRUPAL-CONTRIB-2018-002 is a missing authorization vulnerability in drupal/node_view_permissions, published on 10 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Node view permissions module enables the "View own content" and "View any content" permissions for each content type on the permissions page.

This module has a vulnerability that allows users with these permissions to view unpublished content that they are not otherwise authorized to view.

**This issue was fixed by the maintainer outside of the normal security team protocols. Some issues were patched in 2014 for the 7.x version of this module. The 8.x release was updated within the last 6 months. Both are now flagged as security updates.**

## Which versions are affected by DRUPAL-CONTRIB-2018-002?


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

## How do I fix DRUPAL-CONTRIB-2018-002?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2018-002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2018-002 is a missing authorization vulnerability in drupal/node_view_permissions, published on 10 Jan 2018. 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-2018-002 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2018-002

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