CVE-2016-10549

Sails is an MVC style framework for building realtime web applications. Version 0.12.7 and lower have an issue with the CORS configuration where the value of the origin header is reflected as the value for the Access-Control-Allow-Origin header. This would allow an attacker to make AJAX requests to vulnerable hosts through cross site scripting or a malicious HTML Document, effectively bypassing the Same Origin Policy. Note that this is only an issue when `allRoutes` is set to `true` and `origin` is set to `*` or left commented out in the sails CORS config file. The problem can be compounded when the cors `credentials` setting is not provided. At that point authenticated cross domain requests are possible.

Published: 2018-05-31 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2016-10549 is rated Low Risk (34.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.26%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-10549

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-03-17 0.07% 0.26% +0.19%
2 2023-03-07 0.89% 0.07% -0.82%
3 2022-02-04 0.89%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-10549

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.4 3.0 MEDIUM
CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
1.3 2.7 [email protected]
2.1 2.0 LOW
AV:N/AC:H/Au:S/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:H)
Exploitation requires uncommon or highly specific conditions.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
3.9 2.9 [email protected]

Weakness enumeration for CVE-2016-10549

GitHub Security Advisory for CVE-2016-10549

GHSA-qmv4-jgp7-mf68 · Severity: high · Ecosystem: npm — Sails before 0.12.7 vulnerable to Broken CORS

Affected software / configurations for CVE-2016-10549

Vendor Product Version Raw CPE
sailsjs sails <= 0.12.7 cpe:2.3:a:sailsjs:sails:*:*:*:*:*:node.js:*:*

References for CVE-2016-10549

cvelogic Threat Intelligence