Path Traversal Vulnerability in servey

servey Updated 02 Oct 2025

Summary

06/06/2019
MODERATE
Yes i
Moderate
Not published

GHSA-rv49-54qp-fw42: Path Traversal in servey. Affects servey versions < 3.1.0. Fixed in 3.1.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Servey is an npm package used for conducting surveys. It allows users to create and manage surveys, collect responses, and analyze the data. The package is vulnerable to a Path Traversal attack, which allows attackers to access server files by exploiting insufficient input sanitization.

Vulnerability Detail

The vulnerability in servey arises from a lack of proper input sanitization. Attackers can exploit this by using relative paths to access sensitive server files. This can lead to unauthorized access, disclosure of sensitive information, and potential compromise of the server.

How To Fix

Latest published version: 5.2.6 as of 23 Oct 2026

npm install servey@5.2.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.1.0

This is the first release that contains the fix.

npm install servey@3.1.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

The Path Traversal vulnerability in servey can be fixed by upgrading to the latest version. It is important to promptly update the package to ensure the security of the server and prevent unauthorized access to sensitive files. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for servey →

Share this vulnerability

FAQ

Servey is an npm package used for creating and managing surveys.

A Path Traversal attack is a type of security vulnerability where an attacker can access files or directories outside of the intended scope.

This vulnerability can lead to unauthorized access to sensitive server files, disclosure of confidential information, and potential compromise of the server.

To fix this vulnerability, you should upgrade to the latest version of servey (version 3.1.0 or above).

No, there is no known workaround for this vulnerability. It is recommended to upgrade to the latest version.

Related vulnerabilities

Recent vulnerabilities recorded for servey.

How To Fix

Latest published version: 5.2.6 as of 23 Oct 2026

npm install servey@5.2.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.1.0

This is the first release that contains the fix.

npm install servey@3.1.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback