# DRUPAL-CONTRIB-2019-078: The security team is marking this project unsupported.

> The Drupal module is unsupported with an unfixed known security issue, requiring users to migrate or take over maintenance.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 13 Nov 2019

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

DRUPAL-CONTRIB-2019-078 is a vulnerability in drupal/nexus, published on 13 Nov 2019. 

### Official description

The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: <https://www.drupal.org/node/251466#procedure---own-project---unsupported>

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


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

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

No fix has been published for DRUPAL-CONTRIB-2019-078 yet. Limit exposure of the affected software until one is available.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-078 is a vulnerability in drupal/nexus, published on 13 Nov 2019. 
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2019-078 in the wild and no public exploit code.

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

## Sources

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

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