Skip to content
Fencer Intel
medium 4.4

CVE-2016-10549 json

Sails before 0.12.7 vulnerable to Broken CORS

published 2018-05-31 8 y ago modified 2026-06-17 4 mo ago also GHSA-qmv4-jgp7-mf68 , EUVD-2019-0332

cvss
4.4
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm sails 0.12.7

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 4.4 CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 2.1 AV:N/AC:H/Au:S/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
npm sails
<0.12.7
0.12.7

Affected products

  • HackerOne sails node module

Classification

Weakness
  • CWE-284 Improper Access Control
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.