CVE-2025-47220
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 · uneditedA local file enumeration was found in Keyfactor SignServer versions prior to 7.3.2 .The property VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH, which exists in the PDFSigner and the PAdESSigner, can be set to any path without any restrictions by an admin user. In the case that the provided path points to an existing file, readable by the user running the application server, but is not a recognized image format, it will return this as an error to the clientside, confirming the existences of the file.
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 · moderate confidenceA local file enumeration vulnerability exists in Keyfactor SignServer versions prior to 7.3.2 where the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property in PDFSigner and PAdESSigner components can be set to arbitrary paths by admin users. When a path points to a file readable by the application server but not a recognized image format, the error response confirms the file's existence to the client, enabling enumeration of accessible files on the system.
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< 7.3.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 SignServer versionLocate the installed Keyfactor SignServer version number via the admin UI, API, or by inspecting the installation directory and version file. Common locations include the admin console status page or the signserver.properties/version file in the installation directory.Affected if The installed version is earlier than 7.3.2 (specifically < 7.3.1 as listed in affected versions)
-
Identify active PDFSigner workersQuery the SignServer admin API or inspect the worker configuration files in the deploy directory to identify any configured PDFSigner worker instances.Affected if A PDFSigner worker is active and the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property can be modified by admin users
-
Identify active PAdESSigner workersQuery the SignServer admin API or inspect the worker configuration files in the deploy directory to identify any configured PAdESSigner worker instances.Affected if A PAdESSigner worker is active and the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property can be modified by admin users
-
Inspect VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH propertyAccess the SignServer admin interface or use the CLI to view the current configuration of the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property for any PDFSigner or PAdESSigner workers.Affected if The property is set to a path outside the expected image directory or allows arbitrary file system paths to be configured by admin users
-
Test path enumeration responseAs an admin user, configure the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property to point to a known file on the system that is not a valid image format. Submit a signing request and observe the error response.Affected if The error response differs between existing and non-existing files, confirming file existence enumeration is possible (the error indicates the file exists but is not a valid image)
You are affected if running Keyfactor SignServer version prior to 7.3.2 with PDFSigner or PAdESSigner components where admin users can configure the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property to arbitrary file system paths.
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 · scoped7.3.1
Upgrade to Keyfactor SignServer version 7.3.2 or later which should implement proper path validation and restrict the image path to prevent arbitrary file access enumeration.
SignServer 7.3.2 or later
- 1. Back up your current SignServer configuration and database
- 2. Download SignServer version 7.3.2 or later from the official Keyfactor download portal
- 3. Stop the SignServer application service
- 4. Install the upgraded SignServer version following the standard upgrade documentation
- 5. Restore your configuration from the backup
- 6. Start the SignServer service and verify all services are running
- 7. Verify the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property now properly validates or restricts paths as expected
- 8. Test PDF signing functionality to ensure normal operations are unaffected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47220 — 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-47220 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