CVE-2016-10549
No exploitation reported by the sources we read.
- Published2018-05-31
- Fixed in0.12.7
- WeaknessCWE-284 · CWE-79
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2018-05-3120:29CVE publishedNVD
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.12 | < 0.12.7 | 0.12.7 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.12 | ≤ 0.12.7 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update sails to 0.12.7
Advisories and patches
- sailsjs.orgVendor Advisory
- sailsjs.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVSS 3.04.4read 2026-10-23
- NVDCVSS 2.02.1read 2026-10-23
- CNAweakness (CWE)CWE-284known since 2026-10-23
- NVDweakness (CWE)CWE-79read 2026-10-23
- FIRST EPSSEPSS score0.6 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2020-06-16
Identifiers
- EUVD-2019-0332same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-qmv4-jgp7-mf68same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
- Published
- 2018-05-31
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-qmv4-jgp7-mf68
Frequently asked questions
What is CVE-2016-10549?
Is CVE-2016-10549 actively exploited?
What is the CVSS score for CVE-2016-10549?
Running sails? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-qmv4-jgp7-mf68
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served