CVE-2018-3731: public node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which al

Q: How do I fix CVE-2018-3731?

public.js: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2018-3731 being exploited?

CVE-2018-3731 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-3731 affect?

CVE-2018-3731 affects public.js. Severity is high (CVSS 7.5). public node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which allows a malicious user to read content of any file with known path.

Q: How urgent is CVE-2018-3731?

Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2018-3731 is a high-severity flaw (CVSS 7.5) affecting public.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

public node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which allows a malicious user to read content of any file with known path.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.0% (top 19%)
CISA exploited list	No
Weakness	CWE-22
Published	2018-06-07
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: public.js project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-07 02:29 UTCPublished CVE record published
2026-06-17 01:57 UTCUpdated Record last modified

public.js project public.js DOWNGRADE

Affected: 0.1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1.2

1. Check installed version

npm ls public.js

2. No fixed release: DOWNGRADE to a release before 0.1.2

npm view public.js versions npm install public.js@"<0.1.2"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-3731?

public.js: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-3731 being exploited?

CVE-2018-3731 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-3731 affect?

CVE-2018-3731 affects public.js. Severity is high (CVSS 7.5). public node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which allows a malicious user to read content of any file with known path.

How urgent is CVE-2018-3731?

Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2018-3747 MEDIUM 6.1 UPGRADE The public node module versions <= 1.0.3 allows to embed HTML in file names, which (in certain conditions) mig

References

← Back to latest CVEs