# DRUPAL-CONTRIB-2019-047: In certain configuration cases, when a learning path is configured as semi-private, anonymous users are allowed to join a learning path when they should not.

> Anonymous users can bypass access controls to join semi-private learning paths in specific Drupal 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:** 15 May 2019

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

DRUPAL-CONTRIB-2019-047 is an authentication bypass vulnerability in drupal/opigno_learning_path, published on 15 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In certain configuration cases, when a learning path is configured as semi-private, anonymous users are allowed to join a learning path when they should not.

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


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

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-047 is an authentication bypass vulnerability in drupal/opigno_learning_path, published on 15 May 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-047 in the wild and no public exploit code.

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

## Sources

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

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