# CVE-2025-29316: Information disclosure in n/a

> A physically proximate attacker can bypass watermarks to view sensitive document content if Developer Tools are not disabled via Group Policy.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2025
- **Updated:** 5 May 2025
- **Also known as:** GHSA-wgwq-2crv-c4jj

## What is CVE-2025-29316?

CVE-2025-29316 is a medium-severity vulnerability in n/a, published on 17 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in DataPatrol Screenshot watermark, printing watermark agent v.3.5.2.0 allows a physically proximate attacker to obtain sensitive information. NOTE: the Supplier disputes the Print Job Watermark Bypass claim because the watermark is added by hooking into the OS printing mechanism, and thus is not supposed to be visible when previewing a "generated printout" on screen. The Supplier disputes the Screenshot Watermark Bypass claim because the product's documentation explains the step of setting Developer Tools to Disallowed through AD Group Policy.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-29316?


## How do I fix CVE-2025-29316?

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

## Is CVE-2025-29316 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-29316 and fix it if it is affected.

What it is: CVE-2025-29316 is a medium-severity vulnerability in n/a, published on 17 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29316 exists.

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-2025-29316/ (Markdown: https://insights.sbomify.com/CVE-2025-29316/index.md)
```

## Sources

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

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