CVE-2025-67825
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Nitro PDF Pro for Windows before 14.42.0.34. In certain cases, it displays signer information from a non-verified PDF field rather than from the verified certificate subject. This could allow a document to present inconsistent signer details. The display logic was updated to ensure signer information consistently reflects the verified certificate identity.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNitro PDF Pro for Windows before 14.42.0.34 has a signature verification display flaw where it presents signer information from non-verified PDF fields instead of the verified certificate subject. This allows documents to display misleading signer details that differ from the actual certificate identity, potentially enabling social engineering attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 14.42.0.34CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Nitro PDF Pro versionOpen Windows Settings > Apps & Features, locate Nitro PDF Pro (or Gonitro Nitro Pdf Pro), and note the version number shown. Alternatively, open the application, click Help > About Nitro PDF Pro to view the exact version.Affected if version displayed is below 14.42.0.34
-
Confirm product name matches affected rangeVerify the installed product is specifically Gonitro Nitro Pdf Pro or Nitro PDF Pro for Windows, as other Nitro products may have different version numbering.Affected if product name is Gonitro Nitro Pdf Pro or Nitro PDF Pro for Windows and version is below 14.42.0.34
A user is affected if Nitro PDF Pro for Windows is installed with a version number lower than 14.42.0.34, as the signature verification display flaw exists in those versions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped14.42.0.34
Upgrade Nitro PDF Pro to version 14.42.0.34 or later to ensure signer information consistently reflects the verified certificate identity.
14.42.0.34 or later
- 1. Open Nitro PDF Pro and navigate to Help > About Nitro PDF Pro to verify the current version number
- 2. If the version is earlier than 14.42.0.34, download the latest version from the official Nitro website at www.gonitro.com
- 3. Close any open instances of Nitro PDF Pro
- 4. Run the installer for version 14.42.0.34 or later
- 5. Follow the on-screen prompts to complete the installation
- 6. After installation, verify the new version by checking Help > About Nitro PDF Pro
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67825 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data