Unintended Require vulnerability in larvitbase-www

larvitbase-www Updated 02 Oct 2025

Summary

03/09/2020
MODERATE
No i
Moderate
Not published

GHSA-88h9-fc6v-jcw7: Unintended Require in larvitbase-www. Affects larvitbase-www versions >= 0.0.0. No fix is published. 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

larvitbase-www is an npm package that provides an API endpoint for web applications. It is used to handle HTTP requests and serve static files. The package is vulnerable to an Unintended Require vulnerability, which allows attackers to execute any .js file in the same folder as the server is running.

Vulnerability Detail

The vulnerability in larvitbase-www arises from the package exposing an API endpoint and passing an unsanitized GET parameter to a require() call. This allows attackers to inject malicious code and execute arbitrary JavaScript files on the server. The impact of this vulnerability can be severe, as it grants unauthorized access and control over the server, potentially leading to data breaches, unauthorized modifications, or even complete system compromise.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As there is no fix available, a possible workaround is to implement input validation and sanitization for the GET parameter passed to the require() call. This can help mitigate the risk of code injection. Here's an example of how to sanitize the parameter using the 'sanitize-filename' package:

const sanitizeFilename = require('sanitize-filename');

const sanitizedParam = sanitizeFilename(req.query.param);
require(sanitizedParam);

Conclusion

larvitbase-www is vulnerable to an Unintended Require vulnerability that allows attackers to execute arbitrary JavaScript files on the server. Currently, there is no fix available, so it is recommended to consider using an alternative package. Implementing input validation and sanitization can help mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for larvitbase-www →

Share this vulnerability

FAQ

larvitbase-www is an npm package used to handle HTTP requests and serve static files for web applications.

An Unintended Require vulnerability occurs when a package exposes an API endpoint and passes an unsanitized parameter to a require() call. This allows attackers to execute arbitrary JavaScript files on the server.

The consequences of this vulnerability can be severe. Attackers can gain unauthorized access and control over the server, potentially leading to data breaches, unauthorized modifications, or complete system compromise.

Currently, there is no fix available for this vulnerability in larvitbase-www. It is recommended to consider using an alternative package until a fix is made available.

To mitigate the risk, you can implement input validation and sanitization for the GET parameter passed to the require() call. This can help prevent code injection attacks.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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