What is GHSA-6cj2-92m5-7mvp?

### 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. ### Patches `think-config@1.1.3` patched it, anyone used `think-config` should upgrade to `>=1.1.3` version. ### 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](https://github.com/thinkjs/thinkjs) * Email us at [i@imnerd.org](mailt

How severe is GHSA-6cj2-92m5-7mvp?

GHSA-6cj2-92m5-7mvp has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6cj2-92m5-7mvp?

GHSA-6cj2-92m5-7mvp affects the following packages: think-config (npm). Ecosystems affected: npm.

How do I fix GHSA-6cj2-92m5-7mvp?

Update think-config to 1.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6cj2-92m5-7mvp is resolved across your whole dependency graph.

How do I detect GHSA-6cj2-92m5-7mvp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for think-config, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6cj2-92m5-7mvp 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.

Is GHSA-6cj2-92m5-7mvp actively exploited in the wild?

No public exploit code has been indexed for GHSA-6cj2-92m5-7mvp 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.

When was GHSA-6cj2-92m5-7mvp published, and has it been updated?

GHSA-6cj2-92m5-7mvp was published on August 3, 2021 and was last updated on October 8, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

Improperly Controlled Modification of Object Prototype AttributesGHSA-6cj2-92m5-7mvp

HIGH

GHSA-6cj2-92m5-7mvp is a high-severity (CVSS 7.5) vulnerability in think-config. A fix is available for think-config — see the affected versions and patch details below.

Published

Aug 3, 2021

Updated

Oct 8, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 8, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

think-confignpm

956downloads / week

Description

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.

Patches

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

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]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`think-config`	all versions	1.1.3`npm install think-config@1.1.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for think-config, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update think-config to 1.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6cj2-92m5-7mvp 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.

Frequently Asked Questions

### 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. ### Patches `[email protected]` patched it, anyone used `think-config` should upgrade to `>=1.1.3` version. ### 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](https://github.com/thinkjs/thinkjs) * Email us at [[email protected]](mailt

O3 Security · Impact-Aware SCA

Is GHSA-6cj2-92m5-7mvp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works