How severe is GHSA-qmv4-jgp7-mf68?

No CVSS score has been assigned to GHSA-qmv4-jgp7-mf68 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qmv4-jgp7-mf68?

GHSA-qmv4-jgp7-mf68 affects the following packages: sails (npm). Ecosystems affected: npm.

How do I fix GHSA-qmv4-jgp7-mf68?

Update sails to 0.12.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qmv4-jgp7-mf68 is resolved across your whole dependency graph.

How do I detect GHSA-qmv4-jgp7-mf68 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sails. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qmv4-jgp7-mf68 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qmv4-jgp7-mf68?

O3 pinpoints whether GHSA-qmv4-jgp7-mf68 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qmv4-jgp7-mf68 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qmv4-jgp7-mf68 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-qmv4-jgp7-mf68?

GHSA-qmv4-jgp7-mf68 is classified as CWE-284 (CWE-284), Cross-site Scripting (XSS) (CWE-79). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-qmv4-jgp7-mf68 published, and has it been updated?

GHSA-qmv4-jgp7-mf68 was published on February 18, 2019 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

GHSA-qmv4-jgp7-mf68

GHSA-qmv4-jgp7-mf68 is a CWE-284 vulnerability in sails. O3 Security confirms whether GHSA-qmv4-jgp7-mf68 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sails before 0.12.7 vulnerable to Broken CORS

Also known asCVE-2016-10549

Published

Feb 18, 2019

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

sailsnpm

40Kdownloads / week

Description

Affected versions of sails 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 may 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.

Mitigating Factors

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, because at that point authenticated cross domain requests are possible.

Recommendation

Update to version 0.12.7 or later.

As this vulnerability is primarily a user error, the patch for the vulnerability will simply cause the application to write an error message to the console when a vulnerable configuration is used in a production environment.

Writing a proper CORS configuration is still the responsibility of the user, so it is necessary to check for the error message after installing the patch. Be sure you are not using allRoutes: true with origin:'*', and that you uncomment origin and set it to a reasonable value. Ensure that if origin is set to * that you truly mean for all other websites to be able to make cross-domain requests to your API.

Likewise, ensure credentials is uncommented out and set to the appropriate value. Make sure to explicitly set which origins may request resources via CORS.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sails`	all versions	0.12.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sails. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sails to 0.12.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qmv4-jgp7-mf68 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qmv4-jgp7-mf68 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qmv4-jgp7-mf68. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `sails` 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 may 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. ## Mitigating Factors 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,

O3 Security · Impact-Aware SCA

Is GHSA-qmv4-jgp7-mf68 in your dependencies?

O3 detects GHSA-qmv4-jgp7-mf68 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works