How severe is CVE-2015-9243?

No CVSS score has been assigned to CVE-2015-9243 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-9243?

CVE-2015-9243 affects the following packages: hapi (npm). Ecosystems affected: npm.

How do I fix CVE-2015-9243?

Update hapi to 11.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-9243 is resolved across your whole dependency graph.

How do I detect CVE-2015-9243 in my npm dependencies?

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2015-9243 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-9243, 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-2015-9243?

CVE-2015-9243 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th 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-2015-9243?

CVE-2015-9243 is classified as CWE-284 (CWE-284), CWE-254 (CWE-254). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-9243 published, and has it been updated?

CVE-2015-9243 was published on September 1, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2015-9243 — hapi

CVE-2015-9243 is a CWE-284 vulnerability in hapi. 1 public exploit reference exists, so weaponization risk is real. A fix is available for hapi — see the affected versions and patch details below.

Unsafe Merging of CORS Configuration Conflict in hapi

Published

Sep 1, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk-0.02%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

hapinpm

57Kdownloads / week

Description

When server level, connection level or route level CORS configurations in hapi node module before 11.1.4 are combined and when a higher level config included security restrictions (like origin), a higher level config that included security restrictions (like origin) would have those restrictions overridden by less restrictive defaults (e.g. origin defaults to all origins *).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`hapi`	all versions	11.1.4`npm install hapi@11.1.4`

Affected Products

1 product · 1 configurations

Application

hapihapijs

< 11.1.4

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.

When server level, connection level or route level CORS configurations i…

github.comNVDOct 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hapi to 11.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-9243 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Versions of `hapi` prior to 11.1.4 are affected by a vulnerability that causes route-level CORS configuration to override connection-level or server-level CORS defaults. This may result in a situation where CORS permissions are less restrictive than intended. ## Recommendation Update hapi to version 11.1.4 or later.

O3 Security · Impact-Aware SCA

Is CVE-2015-9243 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works