LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7725: Prototype Pollution

All versions of package worksmith are vulnerable to Prototype Pollution via the setValue function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-7725 affects the npm package worksmith. The reported issue is prototype pollution in its setValue function, which can let unsafe object keys alter shared JavaScript object behavior. In the worst case, this can affect confidentiality, integrity, and availability of applications using the package.

Executive priority

Treat this as urgent only if worksmith is present in production, especially in services processing untrusted input. The severity is critical, but business urgency depends on actual package usage and reachable data flow. There is no source-bundle evidence of active exploitation.

Technical view

The source bundle identifies all versions of worksmith as vulnerable to prototype pollution through setValue. CVSS 3.1 is 9.8: network attack vector, low complexity, no privileges, no user interaction, and high impact across confidentiality, integrity, and availability. No CWE is supplied in the bundle.

Likely exposure

Exposure is likely limited to JavaScript or Node.js applications that include worksmith directly or transitively. Risk is highest where attacker-controlled input can reach the affected setValue behavior. The bundle does not provide package prevalence, fixed versions, or affected downstream products.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates unauthenticated remote exploitability in principle, and the provided exploit maturity value is proof-of-concept. Evidence is insufficient to claim active exploitation.

Researcher notes

Key unknowns are exploit reachability, package maintenance status, and fixed-version availability. The source bundle names setValue as the vulnerable function but does not provide exploit steps, affected applications, or vendor remediation details. Validate reachability before escalating beyond dependency removal or replacement planning.

Mitigation direction

  • Inventory package manifests and lockfiles for direct or transitive worksmith usage.
  • Remove or replace worksmith where feasible after compatibility testing.
  • Check Snyk and upstream package guidance before assuming a patched version exists.
  • Avoid passing attacker-controlled keys or paths into worksmith setValue code paths.
  • Prioritize internet-facing services and workflows handling untrusted JSON or request data.

Validation and detection

  • Search dependency manifests and lockfiles for worksmith.
  • Use dependency scanning to confirm whether worksmith is present transitively.
  • Map any worksmith usage to request, API, queue, or import data paths.
  • Review code paths that call setValue with externally influenced keys.
  • Confirm remediation by rerunning dependency scans after changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-7725 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:C3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-7725Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aworksmith0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.