# DRUPAL-CONTRIB-2022-050: This module enables you to generate PDF versions of content.

> A Drupal module using an outdated dompdf library is vulnerable to security issues, requiring an upgrade to the dependency.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 27 Jul 2022

## What is DRUPAL-CONTRIB-2022-050?

DRUPAL-CONTRIB-2022-050 is a vulnerability in drupal/pdf_api, published on 27 Jul 2022. It can be exploited over the network.

### Official description

This module enables you to generate PDF versions of content.

Some installations of the module make use of the dompdf/dompdf third-party dependency.

Security vulnerabilities exist for versions of dompdf/dompdf before 2.0.0 as described in the [2.0.0 release notes.](https://github.com/dompdf/dompdf/releases/tag/v2.0.0)

## Which versions are affected by DRUPAL-CONTRIB-2022-050?


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

## How do I fix DRUPAL-CONTRIB-2022-050?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2022-050 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-050 is a vulnerability in drupal/pdf_api, published on 27 Jul 2022. It can be exploited over the network.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2022-050 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2022-050

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