# DRUPAL-CONTRIB-2018-025: Simple Taxonomy Revision module enables revisions for taxonomy terms for Drupal 8.

> The Simple Taxonomy Revision module is unsupported with an unfixed security issue, requiring users to remove or replace it.

- **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:** 9 May 2018

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

DRUPAL-CONTRIB-2018-025 is a vulnerability in drupal/simple_revision, published on 9 May 2018. 

### Official description

Simple Taxonomy Revision module enables revisions for taxonomy terms for Drupal 8.

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

The security team marks all unsupported modules critical by default.

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


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

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

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

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2018-025 is a vulnerability in drupal/simple_revision, published on 9 May 2018. 
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2018-025 in the wild and no public exploit code.

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

## Sources

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

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