CVE-2025-25539
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 · uneditedLocal File Inclusion vulnerability in Vasco v3.14and before allows a remote attacker to obtain sensitive information via help menu.
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 confidenceLocal File Inclusion vulnerability in Vasco v3.14 and prior versions allows remote attackers to read sensitive files from the server filesystem through the help menu interface by manipulating file path parameters.
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<= 3.14CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 Onespan Vasco Self Service Portal versionLocate the Self Service Portal installation directory and check for version information in release notes, about page, or configuration files. Common locations include /opt/vasco/ssp, the web application admin interface, or the software bill of materials.Affected if The installed version is v3.14 or any prior version (e.g., 3.13, 3.12, etc.)
-
Verify help menu interface is accessibleConfirm the help menu functionality is enabled and reachable by accessing the help page endpoint (typically /help, /ssp/help, or similar) via the web browser or curl command against the portal URL.Affected if The help menu interface is exposed and accessible without authentication or with standard user credentials
-
Check for unusual file access patterns in web server logsReview web server access logs (typically found in /var/log/httpd, /var/log/nginx, or the application logs directory) for requests to the help menu endpoint containing directory traversal sequences such as ../, ..\, or absolute paths.Affected if Log entries show requests to the help menu with path traversal patterns (e.g., ../../../etc/passwd) targeting sensitive files
-
Inspect help menu configuration for input validationLocate the help menu configuration file or source code (if accessible) and examine whether path parameters are validated, sanitized, or allow unrestricted file system paths.Affected if The help menu accepts unsanitized path parameters and permits directory traversal without restriction
A system is affected if Onespan Vasco Self Service Portal version 3.14 or earlier is installed AND the help menu interface is accessible and allows unrestricted path parameters for file inclusion.
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.
From vendor dataUpgrade to a version newer than v3.14 if available; otherwise, implement strict input validation and path sanitization on the help menu functionality to prevent directory traversal sequences.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25539 — 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-25539 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