What is GHSA-6CJ2-92M5-7MVP?

GHSA-6CJ2-92M5-7MVP is a high-severity security vulnerability in think-config (npm), affecting versions < 1.1.3. It is fixed in 1.1.3.

How severe is GHSA-6CJ2-92M5-7MVP?

GHSA-6CJ2-92M5-7MVP has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of think-config are affected by GHSA-6CJ2-92M5-7MVP?

think-config (npm) versions < 1.1.3 is affected.

Is there a fix for GHSA-6CJ2-92M5-7MVP?

Yes. GHSA-6CJ2-92M5-7MVP is fixed in 1.1.3. Upgrade to this version or later.

Is GHSA-6CJ2-92M5-7MVP exploitable, and should I be worried?

Whether GHSA-6CJ2-92M5-7MVP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-6CJ2-92M5-7MVP is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-6CJ2-92M5-7MVP?

Upgrade think-config to 1.1.3 or later.

GHSA-6CJ2-92M5-7MVP in think-config

Q: How severe is GHSA-6CJ2-92M5-7MVP?

GHSA-6CJ2-92M5-7MVP has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of think-config are affected by GHSA-6CJ2-92M5-7MVP?

think-config (npm) versions < 1.1.3 is affected.

Q: Is there a fix for GHSA-6CJ2-92M5-7MVP?

Yes. GHSA-6CJ2-92M5-7MVP is fixed in 1.1.3. Upgrade to this version or later.

Q: Is GHSA-6CJ2-92M5-7MVP exploitable, and should I be worried?

Whether GHSA-6CJ2-92M5-7MVP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-6CJ2-92M5-7MVP is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-6CJ2-92M5-7MVP?

Upgrade think-config to 1.1.3 or later.

Summary

Improperly Controlled Modification of Object Prototype Attributes

References

https://cwe.mitre.org/data/definitions/1321.html

For more information

If you have any questions or comments about this advisory:

Open an issue in thinkjs/thinkjs
Email us at [email protected]

Impact

The software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

GHSA-6CJ2-92M5-7MVP has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.3); upgrading removes the vulnerable code path.

Affected versions

think-config (< 1.1.3)

Security releases

think-config → 1.1.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

[email protected] patched it, anyone used think-config should upgrade to >=1.1.3 version.

Frequently Asked Questions

What is GHSA-6CJ2-92M5-7MVP? GHSA-6CJ2-92M5-7MVP is a high-severity security vulnerability in think-config (npm), affecting versions < 1.1.3. It is fixed in 1.1.3.
How severe is GHSA-6CJ2-92M5-7MVP? GHSA-6CJ2-92M5-7MVP has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of think-config are affected by GHSA-6CJ2-92M5-7MVP? think-config (npm) versions < 1.1.3 is affected.
Is there a fix for GHSA-6CJ2-92M5-7MVP? Yes. GHSA-6CJ2-92M5-7MVP is fixed in 1.1.3. Upgrade to this version or later.
Is GHSA-6CJ2-92M5-7MVP exploitable, and should I be worried? Whether GHSA-6CJ2-92M5-7MVP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-6CJ2-92M5-7MVP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-6CJ2-92M5-7MVP? Upgrade think-config to 1.1.3 or later.