# CVE-2022-30351: Information disclosure in n/a

> Attackers can recover redacted text and images from PDFs processed by PDFZorro Online due to improper sanitization, leading to sensitive data leakage.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-v82w-4932-72hf

## What is CVE-2022-30351?

CVE-2022-30351 is a high-severity vulnerability in n/a, published on 30 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PDFZorro PDFZorro Online r20220428 using TCPDF 6.2.5, despite having workflows claiming to correctly remove redacted information from a supplied PDF file, does not properly sanitize this information in all cases, causing redacted information, including images and text embedded in the PDF file, to be leaked unintentionally. In cases where PDF text objects are present it is possible to copy-paste redacted information into the system clipboard. Once a document is "locked" and marked for redaction once, all redactions performed after this feature is triggered are vulnerable.

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-1116 (Inaccurate Source Code Comments)

## Which versions are affected by CVE-2022-30351?

It affects 1 product.


Products: Pdfzorro Pdfzorro.

## How do I fix CVE-2022-30351?

No fix has been published for CVE-2022-30351 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-30351 being exploited?

There is no known exploitation of CVE-2022-30351 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30351 and fix it if it is affected.

What it is: CVE-2022-30351 is a high-severity vulnerability in n/a, published on 30 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30351 in the wild and no public exploit code.

Affected product: n/a. 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/CVE-2022-30351/ (Markdown: https://insights.sbomify.com/CVE-2022-30351/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30351
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30351
- OSV: https://osv.dev/vulnerability/CVE-2022-30351

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