# CVE-2024-52277: PDF Document Spoofing in DocuSeal

> Attackers can spoof PDF content by hiding layers that remain visible in print previews, misleading users about document integrity.

- **Severity:** High 8.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2024
- **Updated:** 5 Dec 2024
- **Also known as:** GHSA-x33g-ff5h-73r9

## What is CVE-2024-52277?

CVE-2024-52277 is a high-severity vulnerability in DocuSeal, published on 4 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

User Interface (UI) Misrepresentation of Critical Information vulnerability in DocuSeal allows Content Spoofing.Displayed version does not show the layer flattened version, once download, If printed (e.g. via Google Chrome -> Examine the print preview): Will render the vulnerability only, not all layers are flattened.

This issue affects DocuSeal: through 1.8.1, >1.8.1.

Weakness: CWE-451 (User Interface (UI) Misrepresentation of Critical Information)

## Which versions are affected by CVE-2024-52277?


## How do I fix CVE-2024-52277?

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

## Is CVE-2024-52277 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52277 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52277 and fix it if it is affected.

What it is: CVE-2024-52277 is a high-severity vulnerability in DocuSeal, published on 4 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52277 exists.

Affected product: DocuSeal. 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-2024-52277/ (Markdown: https://insights.sbomify.com/CVE-2024-52277/index.md)
```

## Sources

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

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