How severe is CVE-2018-14381?

CVE-2018-14381 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-14381?

CVE-2018-14381 affects the following packages: pagekit/pagekit (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-14381?

Update pagekit/pagekit to 1.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14381 is resolved across your whole dependency graph.

How do I detect CVE-2018-14381 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pagekit/pagekit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-14381 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2018-14381 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-14381, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-14381?

CVE-2018-14381 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-14381?

CVE-2018-14381 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-14381 published, and has it been updated?

CVE-2018-14381 was published on July 18, 2018 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2018-14381 — pagekit

MEDIUM

CVE-2018-14381 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in pagekit/pagekit. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for pagekit/pagekit — see the affected versions and patch details below.

Pagekit open redirect vulnerability

Also known asGHSA-v47j-rw9h-6m47

Published

Jul 18, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘pagekit/pagekit

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Pagekit before 1.0.14 has a /user/login?redirect= open redirect vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pagekit/pagekit`	all versions	1.0.14`composer require pagekit/pagekit:^1.0.14`

Affected Products

1 product · 1 configurations

Application

pagekitpagekit

< 1.0.14

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Pagekit before 1.0.14 has a /user/login?redirect= open redirect vulnerab…

github.comNVDSep 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pagekit/pagekit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pagekit/pagekit to 1.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14381 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

Pagekit before 1.0.14 has a /user/login?redirect= open redirect vulnerability.

O3 Security · Impact-Aware SCA

Is CVE-2018-14381 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-601Open Redirect

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

pagekit

1.9/10

Maintained0/10

Code-Review1/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jul 18, 2018

First exploit

Sep 14, 2018

Last updated

Oct 20, 2026

Identifiers

CVE-2018-14381

GHSA-v47j-rw9h-6m47

References

Advisorygithub.com · 1.0.14 Advisorynvd.nist.gov · CVE 2018 14381 Packagegithub.com · pagekit Evidencegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting pagekit/pagekit are rated as high or higher (top: critical).

CVE-2025-67164CVE-2025-67165CVE-2024-45967CVE-2023-41005CVE-2022-38916CVE-2022-36573CVE-2019-19013CVE-2019-16669

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026