CVE-2018-16462: Command Injection in apex-publish-static-files

apex-publish-static-files Updated 02 Oct 2025

Summary

01/11/2018
Yes i
Critical
10.0

CVE-2018-16462: Command Injection in apex-publish-static-files. Affects apex-publish-static-files versions < 2.0.1. Fixed in 2.0.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The apex-publish-static-files package is an npm package used for publishing static files in Apex applications. It provides a publish method that allows users to specify a connectString option for connecting to a database. This package is vulnerable to command injection if user input is directly passed into the connectString option.

Vulnerability Detail

The vulnerability in apex-publish-static-files allows an attacker to execute arbitrary commands by injecting malicious input into the connectString option. This can lead to unauthorized access, data leakage, and potential remote code execution. The vulnerability has a severity level of CRITICAL and is classified under CWE-77.

How To Fix

Minimum fixed version

2.0.1

This is the first release that contains the fix.

npm install apex-publish-static-files@2.0.1

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

Workaround

There is no specific workaround mentioned for this vulnerability. Updating to the fixed version is the recommended solution.

Conclusion

The apex-publish-static-files package is vulnerable to command injection, which can lead to serious security risks. It is crucial to update to version 2.0.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for apex-publish-static-files →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary commands, potentially leading to unauthorized access, data leakage, and remote code execution.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file and it will alert you in real-time.

Yes, updating to version 2.0.1 or later of the apex-publish-static-files package fixes this vulnerability.

There are no known exploits for this vulnerability at the moment.

How To Fix

Minimum fixed version

2.0.1

This is the first release that contains the fix.

npm install apex-publish-static-files@2.0.1

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.